fix: patch security vulnerabilities in dependencies#49
Merged
akhileshrangani4 merged 3 commits intomainfrom Mar 9, 2026
Merged
fix: patch security vulnerabilities in dependencies#49akhileshrangani4 merged 3 commits intomainfrom
akhileshrangani4 merged 3 commits intomainfrom
Conversation
Update next 15.5.12 -> 16.1.6 and run npm audit fix to resolve 6 vulnerabilities (hono, @hono/node-server, dompurify, ajv, express-rate-limit, minimatch). tsconfig adjusted for Next.js 16. Made-with: Cursor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Next.js 16 removed the `next lint` CLI command. Switch to calling `eslint` directly and add ignores for .next/ and node_modules/. Made-with: Cursor
Contributor
There was a problem hiding this comment.
Non-blocking feedback (1)
- Align
eslint-config-nextwith the Next 16 upgrade —package.json(Next version bump)
nextis now^16.1.6, but the repo is still oneslint-config-next@^15.5.6. Next’s upgrade guidance recommends upgradingeslint-config-nextalongside Next so lint rules and plugin behavior stay aligned with the framework major version. Consider bumpingeslint-config-nextto^16.1.6(or latest) and refreshingpackage-lock.jsonin this PR.
If you want, I can push a follow-up for item 1 (for example: @CharlieHelps please fix 1).
Contributor
There was a problem hiding this comment.
Non-blocking feedback (1)
- Keep
eslint-config-nextaligned with the Next 16 upgrade — package.json
nextwas upgraded to^16.1.6, buteslint-config-nextis still pinned at^15.5.6. Next’s upgrade guidance recommends upgradingeslint-config-nextalongsidenext, so lint rules and framework expectations stay in sync.
Suggested fix: bumpeslint-config-nextto^16.1.6(orlatest) and regeneratepackage-lock.json.
If you want me to apply this, reply with the item number (for example: @CharlieHelps please fix 1).
Upgrade eslint-config-next to v16 to match the Next.js major version. Drop FlatCompat wrapper and @eslint/eslintrc since eslint-config-next now exports native flat config. Downgrade new set-state-in-effect rule to warn for pre-existing patterns. Made-with: Cursor
alecf
approved these changes
Mar 9, 2026
Member
alecf
left a comment
There was a problem hiding this comment.
works for me - I thought we had to fix some of our fumadocs stuff but maybe not?
Member
Author
|
@alecf ohh, I am not sure about those, Milstead fixed some, and he mentioned these were complaining too, so fixed this. |
Member
|
@akhileshrangani4 oh whoops I just realized this wasn't our |
Member
Author
|
@alecf ahh yes haha |
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.
Summary
npm audit fixto patch 6 vulnerabilities including CVE-2026-24398, CVE-2026-24472, CVE-2026-24473, CVE-2026-24771 (hono), plus @hono/node-server, dompurify, ajv, express-rate-limit, and minimatchjsx: react-jsx, added.next/dev/types/**/*.tsto include)Test plan
npm auditreports 0 vulnerabilitiesnpm run buildsucceeds