Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions framework-boilerplates/remix/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -10,16 +10,16 @@
},
"dependencies": {
"@remix-run/node": "2.17.2",
"@remix-run/react": "2.17.3",
"@remix-run/server-runtime": "2.17.3",
"@remix-run/react": "2.17.5",
"@remix-run/server-runtime": "2.17.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Bump @remix-run/node with the Remix runtime

When this template is installed, @remix-run/node remains pinned at 2.17.2 while the rest of the Remix packages move to 2.17.5; the published @remix-run/node@2.17.2 package depends on its matching @remix-run/server-runtime@2.17.2, so npm will keep a nested vulnerable server-runtime copy even though the top-level direct dependency was bumped. This means the Snyk server-runtime vulnerability this change is meant to fix still remains for anyone using the Remix/Vercel template; update @remix-run/node to the same patched version as the other Remix packages.

Useful? React with 馃憤聽/ 馃憥.

"@vercel/analytics": "^1.2.2",
"@vercel/remix": "2.10.0",
"isbot": "^4",
"react": "^18.2.0",
"react-dom": "^18.2.0"
},
"devDependencies": {
"@remix-run/dev": "2.17.3",
"@remix-run/dev": "2.17.5",
"@remix-run/eslint-config": "2.10.0",
"@types/react": "^18.2.20",
"@types/react-dom": "^18.2.7",
Expand Down