inlining css styles in the head tag via getCssLinks() and custom document does not work anymore in v8.1

[badpenguin]

Describe the bug

After upgrading, and cleaning any temporary data i got a strange issue.

The build + export procedure is working and the generated web site is perfect.

However launching the dev server will start but will not work: when i try to browse to localhost:3000 i get 404 no matter which page's url i try to access.

What can i do to generate some usefull debugging for this issue?

[huv1k]

Hey @badpenguin, from your response it's hard to debug what is wrong. Could you please provide minimal reproduction?

[badpenguin]

Ok i figured it out! but didn't solved it.
First of all i've an errore caused by fs.readFileSync() in page/_documents.tsx and this is causing a 404 instead of an error stack trace.
My problems is that i forked getCssLinks() to inline the CSS styles instead of loading them.
In production mode its working.
In development mode i found a "bug" maybe?
this.context._documentProps.files contains the list of CSS and JS resource to load.
In development mode i have the file dist/_next/static/css/styles.chunk.css
this does not exists on disk, the one on disk is styles.35775087.chunk.css

Instead when i run in production mode it works correctly since they bot
styles.35775087.chunk.css.

At the moment i've mitigated the problem changing the code to use LINK (with URL) instead of STYLE in dev mode if the file does not exists on disk.

The code i use for inlining css in the head via custom _document can be found here:
https://github.com/badpenguin/nextjs-static-generator-boilerplate/blob/master/src/lib/NextHeadWithInlineCss.tsx

[badpenguin]

Source code to test this behaviour with 8.1 has been published here https://github.com/badpenguin/nextjs-static-generator-boilerplate/tree/v8.1.0

[timneutkens]

Sounds like you're doing something unexpected / non-standard.

[badpenguin]

Sounds like you're doing something unexpected / non-standard.

It there a "standard" way to not generate all that pre-load scripts that slows down the initial page load, then?

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.