2 people reported

All time, since Oct 8.

Dynamic CSS in other route's entry

“async-only.module.css is loaded with the async chunk on /other, not on the initial load of /.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/next-js/issues/7446/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 3 a week at the early-October peak.

CSS from next/dynamic leaks into another route's entry CSS. With next build --webpack, a module imported only via next/dynamic on /other appears in /'s entryCSSFiles, with loose or strict cssChunking.

Is this your bug?

File my report
Where
webpack build
Versions
16.5.0-canary.3
Platforms
Linux

Not quite your bug?

  1. Nested next/dynamic CSS missing1 person

Original reports3, newest first

  1. webpack: CSS from next/dynamic on one route is included in another route's entry CSSOn GitHub#99870
  2. webpack: CSS from next/dynamic on one route is included in another route's entry CSSOn GitHub#99869
  3. webpack: CSS from next/dynamic on one route is included in another route's entry CSSOn GitHub#99868

Do you work on Next.js?

Claim its RAP Sheet to see what your users report and answer them in one place.