Repository navigation
Install browser dependencies before snapshot and release builds - #50
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The development snapshot passed all 13 engine/framework test jobs but failed during packaging because the browser build could not import esbuild. The release job had never installed browser/package-lock.json dependencies.
Set up Node 22 with the browser lockfile cache and run npm --prefix browser ci before the module build. This applies to both development snapshots and stable releases.
Validation: clean npm ci and browser bundle build passed locally, with no tracked bundle changes; git diff --check passed. The preceding merged snapshot passed the full 13-job module matrix. Publishing will be verified through the post-merge snapshot workflow.