Following the steps from the previous section, I expected to see a red background but I observed a white background. This means global.css has not been applied to the global-error.tsx page.
Provide environment information
Operating System:
Platform: darwin
Arch: x64
Version: Darwin Kernel Version 22.6.0: Wed Jul 5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64
Available memory (MB): 16384
Available CPU cores: 12
Binaries:
Node: 20.9.0
npm: 10.1.0
Yarn: 1.22.19
pnpm: 9.1.2
Relevant Packages:
next: 15.0.0-canary.171 // Latest available version is detected (15.0.0-canary.171).
eslint-config-next: N/A
react: 19.0.0-rc-778e1ed2-20240926
react-dom: 19.0.0-rc-778e1ed2-20240926
typescript: 5.3.3
Next.js Config:
output: N/A
Which area(s) are affected? (Select all that apply)
Module Resolution
Which stage(s) are affected? (Select all that apply)
Link to the code that reproduces this issue
https://github.com/c-marchese/next-global-styles-in-global-error
To Reproduce
Current vs. Expected behavior
Following the steps from the previous section, I expected to see a red background but I observed a white background. This means global.css has not been applied to the global-error.tsx page.
Provide environment information
Which area(s) are affected? (Select all that apply)
Module Resolution
Which stage(s) are affected? (Select all that apply)
next start (local)
Additional context
Until Next 14.2.7, global-error.tsx shows a red background (see https://github.com/c-marchese/next-global-styles-in-global-error/tree/next14.2.7). Starting Next 14.2.8 – and in the latest canary – it doesn't.
I believe https://github.com/vercel/next.js/pull/69507 might be related to this issue.