vercel/next.js
Readiness BThe React Framework
JavaScript · ★ 141,028 · 100 open issues synced
Contributor readiness
Contributor readiness: 75/100 (grade B)
- Active development
- README
- Contributing guide
- Code of conduct
- CI on pull requests
- Contribution manifest
- Responsive maintainers
Maintainer signals
Maintainers respond in ~<1 day (median first response, measured from real issue sampling; 95% of sampled issues got a response).
This project has no valid contribution manifest yet, so maintainer preferences are unknown.
Local setup
- Package manager: pnpm
- CI: build_and_deploy.yml, build_and_test.yml, build_reusable.yml, code_freeze.yml, create_release_branch.yml, integration_tests_reusable.yml, issue_lock.yml, issue_stale.yml, issue_wrong_template.yml, popular.yml, pr_ci_comment.yml, pr_stack_optimizer.yml, pull_request_auto_label.yml, pull_request_stats.yml, release-next-rspack.yml, retry_deploy_test.yml, retry_test.yml, rspack-nextjs-build-integration-tests.yml, rspack-nextjs-dev-integration-tests.yml, rspack-update-tests-manifest.yml, sync_backport_canary_release.yml, test-turbopack-rust-bench-test.yml, test_e2e_deploy_release.yml, test_e2e_project_reset_cron.yml, test_examples.yml, triage.yml, trigger_release.yml, turbopack-benchmark.yml, turbopack-nextjs-build-integration-tests.yml, turbopack-nextjs-dev-integration-tests.yml, turbopack-update-tests-manifest.yml, update_fonts_data.yml, update_react.yml, update_react_poller.yml, upload-tests-manifest.yml, upload_preview_tarballs.yml
Links
Open issues
Sign in to see which issues fit your skills- #95709 Turbopack Rust React Compiler renames catch bindings to temporaries without emitting the rebinding statement, causing ReferenceError in catch bodies
intermediate · unassigned
- #85679 Broken next-lint-to-eslint-cli codemod
intermediate · unassigned · Linting · Instrumentation
- #73097 Relay multi-project configuration doesn't work
intermediate · unassigned · bug
- #82117 Duplicate Location and x-nextjs-stale-time in Header using redirect/permanentRedirect alongside dynamic 'force-static'
intermediate · unassigned · linear: next · Headers
- #95698 Turbopack bundling issue (webpack behaviour is correct, turbopack does not tree shake correctly)
intermediate · unassigned · Performance · Turbopack
- #95648 App Router: root route's server-side usePathname() is "/index" on Vercel, causing hydration mismatch (#418)
intermediate · assigned · Runtime
- #95635 Duplicate identifier 'PagesPageConfig' when Building a Page Router NextJS Application without an pages/api route
intermediate · unassigned · TypeScript
- #74494 useSearchParams() should not need to be wrapped in a suspense boundary
intermediate · unassigned
- #88343 Race condition in action queue can undo navigation
intermediate · unassigned · Linking and Navigating · linear: next
- #54708 Next.js development high memory usage
intermediate · unassigned · linear: next
- #91540 [cacheComponents] Forward navigation restores inapplicable state from previously-visited pages
intermediate · unassigned
- #82344 draftMode not accurate in middleware with nodejs runtime
intermediate · unassigned · Draft Mode
- #93923 Bug: `history.pushState` to a new URL reverts when route has a prefetched `<Link>` + `proxy.ts` cookie-based redirect
intermediate · unassigned · Middleware · Linking and Navigating · Runtime · Dynamic Routes
- #94740 image-component.js: deviceSizes.sort() crashes on frozen array in production SSR (Next.js 16)
intermediate · assigned · Image (next/image)
- #65335 RSC and CDN interaction makes next.js inefficient for highload projects
intermediate · unassigned · Performance · linear: next
- #62228 404 page isn't server rendered when using notFound()
intermediate · unassigned · bug · Linking and Navigating
- #64776 Route handler does not receive searchParams set by middleware without runtime edge
intermediate · unassigned · bug
- #95637 NextRouter was not mounted when using the documented custom-server API in production, triggered by any useRouter() call inside _app
intermediate · unassigned
- #81161 Turbopack dev server uses too much RAM and CPU
intermediate · unassigned · Performance · Turbopack · linear: turbopack
- #87737 Turbopack generates external module references with hashes that don't match installed packages when node_modules structure differs
intermediate · unassigned · Output · Turbopack · linear: turbopack
- #95545 E696 `Invariant: Expected workUnitAsyncStorage to have a store` intermittently fails `next build` static export on random pages under machine load
intermediate · unassigned · Runtime
- #95567 Navigation Waits for RSC Tree Before Updating UI (App Router)
intermediate · unassigned · Dynamic Routes
- #95494 Turbopack dev: imported binding left unrewritten (ReferenceError) when referenced after a for...of whose body ends in an unconditional return
intermediate · unassigned
- #95559 Flight payload repeats the full chunk URL list for every client module reference (~29% of SSR HTML is duplicated chunk URLs)
intermediate · unassigned · Performance · Turbopack
- #88986 Link doesn't scroll to section anchor (by id) again
intermediate · unassigned · Linking and Navigating · linear: next
- #49927 DraftMode __prerender_bypass cookie SameSite LAX instead of None
intermediate · unassigned · linear: next
- #86479 `next dev`: Instrumentation hook is still analyzed for the edge runtime despite never running in the edge runtime
intermediate · unassigned · Middleware · linear: next · Instrumentation
- #89192 [Turbopack] Duplicate class definitions across route chunks, breaking `instanceof`
intermediate · unassigned · Turbopack
- #95588 Streamed Suspense boundaries never reveal in documents that load hidden (background tab, occluded window, iOS standalone PWA) — vendored react-dom gates the first $RB reveal batch on requestAnimationFrame
intermediate · assigned · Upstream · Performance · Runtime · React
- #76612 `"use cache"` doesn't work for route handlers
intermediate · unassigned · Cache Components
Showing 30 of 100 open issues — the rest are on GitHub.