Unverified Commit ace529ad authored by Tim Neutkens's avatar Tim Neutkens Committed by GitHub

Turbopack build: Fix next-image-legacy test (#67989)

The path is still correct just more specific, so changed the test to
match both.
<!-- 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 b925a1bf
...@@ -117,7 +117,7 @@ describe('Build Error Tests for basePath', () => { ...@@ -117,7 +117,7 @@ describe('Build Error Tests for basePath', () => {
"Module not found: Can't resolve '../public/foo/test-rect-broken.jpg" "Module not found: Can't resolve '../public/foo/test-rect-broken.jpg"
) )
// should contain the importing module // should contain the importing module
expect(stderr).toContain('./pages/static-img.js') expect(stderr).toContain('pages/static-img.js')
}) })
} }
) )
......
...@@ -12763,11 +12763,10 @@ ...@@ -12763,11 +12763,10 @@
"Static Image Component Tests for basePath production mode Should allow provided width and height to override intrinsic", "Static Image Component Tests for basePath production mode Should allow provided width and height to override intrinsic",
"Static Image Component Tests for basePath production mode Should automatically provide an image height and width", "Static Image Component Tests for basePath production mode Should automatically provide an image height and width",
"Static Image Component Tests for basePath production mode Should use immutable cache-control header even when unoptimized", "Static Image Component Tests for basePath production mode Should use immutable cache-control header even when unoptimized",
"Static Image Component Tests for basePath production mode Should use immutable cache-control header for static import" "Static Image Component Tests for basePath production mode Should use immutable cache-control header for static import",
],
"failed": [
"Build Error Tests for basePath production mode should throw build error when import statement is used with missing file" "Build Error Tests for basePath production mode should throw build error when import statement is used with missing file"
], ],
"failed": [],
"pending": [ "pending": [
"Static Image Component Tests for basePath development mode Should add a blur placeholder to statically imported jpg", "Static Image Component Tests for basePath development mode Should add a blur placeholder to statically imported jpg",
"Static Image Component Tests for basePath development mode Should add a blur placeholder to statically imported png", "Static Image Component Tests for basePath development mode Should add a blur placeholder to statically imported png",
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