fix(security+lint): upgrade Next.js 16.2.10, add ESLint, fix React Compiler errors#86
Draft
caimanoliveira wants to merge 1 commit into
Draft
fix(security+lint): upgrade Next.js 16.2.10, add ESLint, fix React Compiler errors#86caimanoliveira wants to merge 1 commit into
caimanoliveira wants to merge 1 commit into
Conversation
… Compiler errors - Upgrade next 16.2.0 → 16.2.10 (fixes DoS, XSS, cache poisoning, middleware bypass CVEs) - Fix ws vulnerability via npm audit fix - Add eslint + eslint-config-next devDependencies (next lint removed in Next.js 16) - Create eslint.config.mjs with core-web-vitals + typescript config - Update npm lint script from `next lint` to `eslint .` - Fix react-hooks/set-state-in-effect errors in useProducts, useSources, useStages, useLeads by restructuring async fetch to inline IIFE inside useEffect - Fix react-hooks/preserve-manual-memoization in useLeads by flattening filter object deps - Fix react/no-unescaped-entities in kanban-column.tsx - Fix react-hooks/purity in PlanoAcaoWidget: move Date.now() to lazy useState initializer Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QPbvJGipRmTDDbRnQnqFLY
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 participants
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
next16.2.0 → 16.2.10 (resolves 14 CVEs: DoS via Server Components, XSS via CSP nonces, middleware/proxy bypass, cache poisoning, SSRF via WebSocket)wsmemory exhaustion vulnerability vianpm audit fixeslint+eslint-config-nextdevDependencies; createeslint.config.mjswithcore-web-vitals + typescriptconfig; updatenpm run lintscript (Next.js 16 removednext lint)react-hooks/set-state-in-effectinuseProducts,useSources,useStages,useLeads,leads/[id]/page.tsx— refactored async fetch to inline async IIFE insideuseEffectinstead of passing named function referencesreact-hooks/preserve-manual-memoizationinuseLeads— flattened filter object to individual primitive deps matching compiler inferencereact/no-unescaped-entitiesinkanban-column.tsx— replaced bare"with“/”react-hooks/purityinPlanoAcaoWidget— movedDate.now()call to auseStatelazy initializer via externaldefaultDeadline()helperTest plan
npm run build— compiles successfully (22 routes, TypeScript clean)npm run lint— 0 errors, 14 warnings (unused vars, pre-existing)Generated by Claude Code