c5c2c9d38b
It’s possible that global CSS imports, that come from node_modules, are marked as side effect free because of possible `sideEffects: false` in the external package's package.json. In that case, we still need to handle global CSS imports as side effects on the server because we need to collect them and avoid tree-shaking for these modules. You can take a look at the test case to see what exactly happened. ## Bug - [ ] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) |
||
|---|---|---|
| .. | ||
| blocks | ||
| helpers.ts | ||
| index.ts | ||
| utils.ts | ||