rsnext/test
Tim Neutkens aedd858598
Fix should have correct module not found error test (#57383)
The module not found check is a bit different in 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 #

-->
2023-11-05 18:57:21 +01:00
..
.stats-app tweak stats action to pull in runtime sizes (#58005) 2023-11-03 23:39:37 +00:00
development Remove installCommand on typescript-auto-install and pnpm-support (#58039) 2023-11-05 18:32:10 +01:00
e2e Remove installCommand on streaming-ssr test (#58037) 2023-11-05 13:30:12 +01:00
examples feat(cli): introduce --tailwind flag (#46927) 2023-03-16 16:06:27 +01:00
integration Fix should have correct module not found error test (#57383) 2023-11-05 18:57:21 +01:00
lib Remove setPnpmResolutionMode as default is highest (#57828) 2023-11-04 21:19:51 +01:00
production Remove installCommand on typescript-auto-install and pnpm-support (#58039) 2023-11-05 18:32:10 +01:00
unit fix: updates for resuming postponed in minimal mode (#57375) 2023-11-03 21:17:45 +00:00
.gitignore ci(workflow): enable test trace upload (#51107) 2023-06-12 17:14:13 +00:00
build-turbopack-tests-manifest.js Turbopack: reenable some skipped test cases (#57177) 2023-10-21 15:11:27 -07:00
jest-setup-after-env.ts Decrease default test timeouts (#56116) 2023-09-27 23:55:20 +00:00
readme.md refactor: split up CONTRIBUTING.md (#40515) 2022-09-16 14:54:58 -07:00
test-file.txt
turbopack-tests-manifest.json Move ReactRefreshLogBox-builtins tests to inline snapshots (#57952) 2023-11-02 21:32:52 +00:00

See Testing for more information on how you can run/write/debug tests for Next.js.