ci: wait for npm packages to be available before publishing vscode extension (#312)

Add a script to wait for published npm packages to be available on the
registry before publishing the vscode extension. This prevents the vscode
extension from being published with outdated dependencies.

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: mizdra

.github/workflows/release.yml

@@ -38,6 +38,9 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_CONFIG_PROVENANCE: true
+      - name: Wait for npm packages to be available
+        if: steps.changesets.outputs.publishedPackages != '[]'
+        run: ./scripts/wait-for-npm-packages.sh '${{ steps.changesets.outputs.publishedPackages }}'
       - run: npx @vscode/vsce publish --no-git-tag-version --skip-duplicate
         if: steps.changesets.outputs.hasChangesets == 'false'
         working-directory: packages/vscode

scripts/wait-for-npm-packages.sh

@@ -0,0 +1,34 @@
+#!/bin/bash
+set -euo pipefail
+
+# Wait for published npm packages to be available on the registry
+# Usage: ./wait-for-npm-packages.sh '<publishedPackages JSON>'
+# Example: ./wait-for-npm-packages.sh '[{"name":"@css-modules-kit/core","version":"0.8.1"}]'
+
+published_packages="$1"
+
+# Parse published packages and wait for each to be available on npm registry
+echo "$published_packages" | jq -r '.[] | "\(.name)@\(.version)"' | while read -r package; do
+  echo "Waiting for $package to be available on npm registry..."
+  max_attempts=10
+  attempt=1
+
+  while [ $attempt -le $max_attempts ]; do
+    if npm view "$package" version &> /dev/null; then
+      echo "✓ $package is now available on npm registry"
+      echo ""
+      break
+    fi
+
+    if [ $attempt -eq $max_attempts ]; then
+      echo "✗ Timeout waiting for $package to be available"
+      exit 1
+    fi
+
+    echo "  Attempt $attempt/$max_attempts: not yet available, waiting 10 seconds..."
+    sleep 10
+    attempt=$((attempt + 1))
+  done
+done
+
+echo "All packages are now available on npm registry"