Next.js closed 1,500 github issues in one month and shipped experimental turbopack chunking the…
next.js closed 1,500 github issues in one month and shipped experimental turbopack chunking the same week. that is not a release schedule, that is a confession — the framework was stuck and someone finally drew a line in the backlog.
the next phase of frontend is going to be won by the team that treats issue triage like the product, not the boring part.
Context
The Next.js blog says the backlog peaked at 3,109 open issues in January 2025 and stood at 2,244 on 10 August 2026. Roughly three weeks later it had closed 1,462 issues and brought the backlog below 1,000, with 218 new reports arriving, and that includes some issues maintainers closed outside the review. The post describes an AI research agent, and a Next.js Bluesky post says the team closed 1,500 issues in one month with a closability agent. The turbopackChunking option is experimental, is documented in Next.js 16.3 or later, and the docs say it is not recommended for production.
The 1,462 closed in about three weeks is the vendor's figure, and the 1,500 in one month is its headline rounding. Both include some closures outside the review. It is not a current count. The docs say the chunking options are available in Next.js 16.3 or later, and the post carrying them has a metadata date of 3 September 2026. No inspected source dates the feature's first availability, and a 29 June 2026 preview post does not establish that the feature was present, so shipped the same week is unverified either way. The post itself says the backlog was a long-term accumulation, and that inactivity automation had mixed results. That this is a confession and that the framework was stuck are the author's opinion, as is treating triage as the product.
Related work
- Next.js 16.3 ↗Release that contains the chunking option.
- turbopackChunking (Next.js docs) ↗Marked experimental.
Watch next
- Next.js's backlog count after the review.
Sources
Provenance
The note above is reproduced unedited from the original post, first published on Threads on 6 September 2026 at 14:03 IST. Sources are the papers and datasets the note draws on.
View the original post ↗Embed this note
More notes
The air is now being asked to keep its own ledger
the air is now being asked to keep its own ledger: ecmwf’s aifs compo becomes the first ai model to forecast atmospheric composition globally every three hours, cleanair simulates 365 days of pm2.5 over china in ten seconds, and a unified framework maps six pollutants at one kilometer across the whole country. the air now files its own composition report.
read the note →The current is now being asked to draw its own map
the current is now being asked to draw its own map: china’s langya 2.0 predicts six ocean phenomena including internal waves and mesoscale eddies, a deep net called wenhai resolves eddies globally with air sea flux formulas built in, and scripps infers surface currents from the way temperature patterns deform in satellite images. the ocean now files its own circulation report.
read the note →The soil is now being asked to report its own carbon
the soil is now being asked to report its own carbon: a nix color sensor paired with generative data augmentation predicts soil organic carbon without a lab, random forest drives 74 percent of soil health mapping studies, and sentinel 2 tracks five year carbon change across france and italy from 922 samples. the dirt now files its own carbon account.
read the note →