fix dependency security issues - #9
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 972165a7d8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "description": "RagIndex landing page — dark hero with looping video, marquee and liquid-glass UI.", | ||
| "engines": { | ||
| "node": ">=18" | ||
| "node": ">=22.22.0" |
There was a problem hiding this comment.
Fresh local installations still direct users to unsupported runtimes: frontend/.nvmrc selects Node 20, while the README and setup/launcher scripts advertise Node 18+. The newly added react-router@8.3.0 and this package now require Node >=22.22.0, so anyone following those entry points gets an unsupported install, and npm configurations with engine-strict=true reject it outright. Update the .nvmrc, prerequisites, and setup diagnostics alongside this engine change, or retain dependencies compatible with the documented Node versions.
Useful? React with 👍 / 👎.
1 participant
What changed
Why
The existing lockfile retained vulnerable React Router and turbo-stream releases. A newly published React Router advisory affects all available React Router DOM 7.x versions, so resolving the audit required moving to the patched React Router 8 package.
Impact
The frontend keeps the same routes and browser behavior while moving to supported dependency versions. CI and the frontend Docker build now use Node 22.
Validation
npm cinpm audit --audit-level=moderate(0 vulnerabilities)npm run buildnpm run test(15 tests passed)npm ls --all