Skip to content

fix: patch security vulnerabilities in dependencies#49

Merged
akhileshrangani4 merged 3 commits intomainfrom
fix/security-vulnerabilities-march-2026
Mar 9, 2026
Merged

fix: patch security vulnerabilities in dependencies#49
akhileshrangani4 merged 3 commits intomainfrom
fix/security-vulnerabilities-march-2026

Conversation

@akhileshrangani4
Copy link
Member

@akhileshrangani4 akhileshrangani4 commented Mar 9, 2026

Summary

Test plan

  • npm audit reports 0 vulnerabilities
  • npm run build succeeds
  • Verify app works correctly on dev server

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
@vercel
Copy link

vercel bot commented Mar 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tambo-strudel Ready Ready Preview, Comment Mar 9, 2026 10:08pm

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
Copy link
Contributor

@charliecreates charliecreates bot left a comment

Choose a reason for hiding this comment

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

Non-blocking feedback (1)
  1. Align eslint-config-next with the Next 16 upgrade — package.json (Next version bump)
    next is now ^16.1.6, but the repo is still on eslint-config-next@^15.5.6. Next’s upgrade guidance recommends upgrading eslint-config-next alongside Next so lint rules and plugin behavior stay aligned with the framework major version. Consider bumping eslint-config-next to ^16.1.6 (or latest) and refreshing package-lock.json in this PR.

If you want, I can push a follow-up for item 1 (for example: @CharlieHelps please fix 1).

Copy link
Contributor

@charliecreates charliecreates bot left a comment

Choose a reason for hiding this comment

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

Non-blocking feedback (1)
  1. Keep eslint-config-next aligned with the Next 16 upgrade — package.json
    next was upgraded to ^16.1.6, but eslint-config-next is still pinned at ^15.5.6. Next’s upgrade guidance recommends upgrading eslint-config-next alongside next, so lint rules and framework expectations stay in sync.
    Suggested fix: bump eslint-config-next to ^16.1.6 (or latest) and regenerate package-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
Copy link
Member

@alecf alecf left a comment

Choose a reason for hiding this comment

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

works for me - I thought we had to fix some of our fumadocs stuff but maybe not?

@akhileshrangani4
Copy link
Member Author

@alecf ohh, I am not sure about those, Milstead fixed some, and he mentioned these were complaining too, so fixed this.

@akhileshrangani4 akhileshrangani4 merged commit 2e8f08d into main Mar 9, 2026
5 checks passed
@alecf
Copy link
Member

alecf commented Mar 9, 2026

@akhileshrangani4 oh whoops I just realized this wasn't our tambo repo, thats where I saw the issue

@akhileshrangani4
Copy link
Member Author

@alecf ahh yes haha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants