-
Notifications
You must be signed in to change notification settings - Fork 27.6k
Issues: vercel/next.js
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Update Turbopack development test manifest
CI approved
Approve running CI for fork
tests
#75946
opened Feb 12, 2025 by
vercel-release-bot
Loading…
Update Turbopack production test manifest
CI approved
Approve running CI for fork
tests
#75568
opened Feb 2, 2025 by
vercel-release-bot
Loading…
Update Rspack production test manifest
CI approved
Approve running CI for fork
tests
#75466
opened Jan 30, 2025 by
vercel-release-bot
Loading…
Update Rspack development test manifest
CI approved
Approve running CI for fork
tests
#75465
opened Jan 30, 2025 by
vercel-release-bot
Loading…
fix: using punycode from punycode repo and not native node
CI approved
Approve running CI for fork
type: next
#75394
opened Jan 28, 2025 by
wowczarczyk
Loading…
Update font data
CI approved
Approve running CI for fork
Font (next/font)
Related to Next.js Font Optimization.
type: next
#75380
opened Jan 28, 2025 by
vercel-release-bot
Loading…
Fix Accessing element.ref was removed in React 19
CI approved
Approve running CI for fork
type: next
#74334
opened Dec 27, 2024 by
oliviertassinari
Loading…
feat(eslint-plugin): add minimal built-in flat presets
CI approved
Approve running CI for fork
type: next
#73873
opened Dec 13, 2024 by
SukkaW
Loading…
fix(build): fix css modules out of order issue from libraries
CI approved
Approve running CI for fork
tests
type: next
#70087
opened Sep 13, 2024 by
piratetaco
Loading…
ProTip!
Exclude everything labeled
bug with -label:bug.