Unverified Commit 6f2fba4c authored by Tim Neutkens's avatar Tim Neutkens Committed by GitHub

Turbopack build: Fix css-modules tests (#68068)

Fixes a bunch of CSS related tests that were written based on the
`.next` folder instead of the rendered page, added snapshots for
Turbopack.

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->
parent 025db7df
...@@ -7604,22 +7604,22 @@ ...@@ -7604,22 +7604,22 @@
"Has CSS Module in computed styles in Development should have CSS for page", "Has CSS Module in computed styles in Development should have CSS for page",
"Has CSS Module in computed styles in Production production mode should have CSS for page", "Has CSS Module in computed styles in Production production mode should have CSS for page",
"Has CSS Module in computed styles in Production production mode should have compiled successfully", "Has CSS Module in computed styles in Production production mode should have compiled successfully",
"Valid CSS Module Usage from within node_modules production mode should have compiled successfully" "Valid CSS Module Usage from within node_modules production mode should have compiled successfully",
],
"failed": [
"3rd Party CSS Module Support production mode should've emitted a single CSS file", "3rd Party CSS Module Support production mode should've emitted a single CSS file",
"3rd Party CSS Module Support production mode should've injected the CSS on server render", "3rd Party CSS Module Support production mode should've injected the CSS on server render",
"Basic CSS Module Support production mode should've emitted a single CSS file", "Basic CSS Module Support production mode should've emitted a single CSS file",
"Basic CSS Module Support production mode should've injected the CSS on server render",
"CSS Module Composes Usage (Basic) production mode should've emitted a single CSS file", "CSS Module Composes Usage (Basic) production mode should've emitted a single CSS file",
"CSS Module Composes Usage (External) production mode should have compiled successfully", "Valid CSS Module Usage from within node_modules production mode should've emitted a single CSS file",
"CSS Module Composes Usage (External) production mode should've emitted a single CSS file",
"Catch-all Route CSS Module Usage production mode should've emitted a single CSS file", "Catch-all Route CSS Module Usage production mode should've emitted a single CSS file",
"Dynamic Route CSS Module Usage production mode should've emitted a single CSS file", "Dynamic Route CSS Module Usage production mode should've emitted a single CSS file",
"Valid CSS Module Usage from within node_modules production mode should've emitted a single CSS file", "Basic CSS Module Support production mode should've injected the CSS on server render",
"Valid CSS Module Usage from within node_modules production mode should've prerendered with relevant data", "Valid CSS Module Usage from within node_modules production mode should've prerendered with relevant data"
"Valid Nested CSS Module Usage from within node_modules production mode should have compiled successfully", ],
"failed": [
"CSS Module Composes Usage (External) production mode should have compiled successfully",
"CSS Module Composes Usage (External) production mode should've emitted a single CSS file",
"Valid Nested CSS Module Usage from within node_modules production mode should've emitted a single CSS file", "Valid Nested CSS Module Usage from within node_modules production mode should've emitted a single CSS file",
"Valid Nested CSS Module Usage from within node_modules production mode should have compiled successfully",
"Valid Nested CSS Module Usage from within node_modules production mode should've prerendered with relevant data" "Valid Nested CSS Module Usage from within node_modules production mode should've prerendered with relevant data"
], ],
"pending": [ "pending": [
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment