Bug: ajv-keywords@5.1.1 returns 400 from StackBlitz npm proxy #2080

Describe the bug

Bug: ajv-keywords@5.1.1 returns 400 from StackBlitz npm proxy

Environment

• WebContainer API
• Browser: Chrome (latest)

Problem

When installing dependencies inside a WebContainer, ajv-keywords@5.1.1 fails with a 400 error from the StackBlitz npm proxy.

The request URL is:

https://t.staticblitz.com/w/v17/h/e/ajv-keywords@5.1.1?o=https://stackblitz.com

Returns:

HTTP 400

However, the previous version resolves fine:

https://t.staticblitz.com/w/v17/h/e/ajv-keywords@5.1.0?o=https://stackblitz.com

This causes npm install to fail with:

npm error EIO: 'ajv-keywords@5.1.1' not found in cache, try running install again

Root Cause

It appears ajv-keywords@5.1.1 has not been synced to the StackBlitz npm proxy cache. The package exists on the public npm registry but is not available via t.staticblitz.com.

Workaround

Pinning to ajv-keywords@5.1.0 via overrides in package.json works around the issue, but this should not be necessary.

Request

Please manually trigger a sync for ajv-keywords@5.1.1 in the proxy cache.

Link to the blitz that caused the error

https://t.staticblitz.com/w/v17/h/e/ajv-keywords@5.1.1?o=https://stackblitz.com

Steps to reproduce

1. Create a WebContainer project with a package.json that depends on ajv-keywords@5.1.1 (directly or transitively, e.g. via umi@4.6.42).
2. Run npm install inside the WebContainer.
3. Observe that the following request returns HTTP 400:

   https://t.staticblitz.com/w/v17/h/e/ajv-keywords@5.1.1?o=https://stackblitz.com
   

4. npm install exits with:

   npm error EIO: 'ajv-keywords@5.1.1' not found in cache, try running install again
   

Expected behavior

ajv-keywords@5.1.1 should be available via the StackBlitz npm proxy, just like ajv-keywords@5.1.0 is. The install should complete successfully without requiring consumers to manually pin to an older version.

Parity with Local

• I have run the project in my local machine and I could not reproduce the issue.

Screenshots

No response

Platform

• OS: [e.g. macOS, Windows, Linux]
• Browser: [e.g. Chrome, Safari, Firefox]
• Version: [e.g. 91.1]

Additional context

No response