Skip to content
Open
Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion _config/nodeAPI/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
"lint": "eslint . --ext .js,.jsx,.ts,.tsx"
},
"dependencies": {
"next": "^14.1.4",
"next": "^16.1.5",
Copy link

Choose a reason for hiding this comment

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

eslint-config-next version mismatch with Next.js 16

Medium Severity

The next dependency is upgraded to ^16.1.5, but eslint-config-next remains at ^14.1.4. These packages are designed to work together and should be kept in sync. The ESLint config for Next.js 14 may not correctly validate Next.js 16 patterns, potentially missing new linting rules or incorrectly flagging valid Next.js 16 code. The eslint-config-next dependency should be updated to ^16.1.5 to match.

Additional Locations (1)

Fix in Cursor Fix in Web

Copy link

Choose a reason for hiding this comment

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

Export script broken by removed next export command

High Severity

The upgrade to Next.js 16 breaks the existing export script at line 12, which uses next export -o ipfs. The next export command was fully removed in Next.js 16 and now throws an error: "next export has been removed in favor of 'output: export' in next.config.js." Static exports now require setting output: 'export' in next.config.js instead of using a CLI command.

Fix in Cursor Fix in Web

"react": "18.2.0",
"react-dom": "^18.2.0",
"styled-jsx": "^5.1.2"
Expand Down
Loading