Repository navigation
Fix high-severity dependencies in Gatsby and React examples - #123
Open
miguelcalderon wants to merge 2 commits into
Open
miguelcalderon wants to merge 2 commits into
miguelcalderon wants to merge 2 commits into
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
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.
What
Fix high-severity development-server path traversal in the Gatsby and React examples, and redirect header exposure in React. Update the affected dependencies and apply small, versioned npm patches to preserve one-byte/range responses and close unused streams on header-only (
HEAD) requests.Add HTTP regression tests to the existing CI job and document the tested Node.js 24 runtime and patch installation requirements.
Validation: the security suite, existing Gatsby tests, both production builds, and rendered-PDF checks passed. Clean installs with and without development dependencies apply the patches; repeat application succeeds, and incompatible patches fail. React audits at zero high/critical findings. The branch includes the latest
main, preserving the Gatsby decoder fix from #120. After merging, the security suite, Gatsby tests/build, development 404 page, rendered PDF, and tracked-file Biome checks pass. Gatsby has two remaining high audit findings related to redirects, covered separately by #116.Known limitation, deferred for this security update: React's dev server returns 404 for
/static/js/bundlewithAccept: application/jsoninstead of generating a helper HTML page. Normal.jsrequests, browser navigation, and the PDF viewer still work.Type
Checklist
pnpm run formatpasses (Biome) — all tracked files passed the equivalent read-only Biome check.startandstart:e2escripts inpackage.jsonSERVER_DIR=examples/<name> pnpm run testpasses (Playwright smoke test) — equivalent checks used isolated ports for both examples; Gatsby used/example1/, and both PDFs fully rendered.README.mdincluded with prerequisites, setup, and usage@nutrient-sdk/viewerversion