Skip to content

chore: update http import lock data - #505

Merged
SyMind merged 1 commit into
mainfrom
push-http-import-lock-data
Sep 14, 2026
Merged

SyMind merged 1 commit into
mainfrom
push-http-import-lock-data

Conversation

@SyMind

@SyMind SyMind commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

Summary

Commit the buildHttp lockfile cache (http-import.lock.data/) for the rspack/http-import example instead of gitignoring it.

Rspack's experiments.buildHttp (aligned with webpack) defaults frozen to true in production mode: a build with a lockfile entry but no matching content in the lockfile cache fails with:

ERROR in ./src/index.js 1:1-55
  × https://www.unpkg.com/the-answer is missing content in the lockfile cache, but lockfile is frozen

This broke the examples suite in rstack-ecosystem-ci, which runs rspack build (production mode by default) in this example with only http-import.lock committed.

Changes:

  • Delete rspack/http-import/.gitignore so the cache directory is tracked.
  • Commit the cached content for https://www.unpkg.com/the-answer under http-import.lock.data/.
  • Refresh valid_until in http-import.lock to match the regenerated cache.

Related links

@SyMind
SyMind merged commit 220d3d9 into main Sep 14, 2026
1 check passed
@SyMind
SyMind deleted the push-http-import-lock-data branch September 14, 2026 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant