Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: CI #2

Merged
merged 2 commits into from
May 18, 2024
Merged

fix: CI #2

merged 2 commits into from
May 18, 2024

Conversation

devjiwonchoi
Copy link

CI is failing since:

  • create-next-app tests it were out of describe, not skipped
  • added --no-turbo flag for CI

@devjiwonchoi devjiwonchoi merged commit 6048467 into canary May 18, 2024
@devjiwonchoi devjiwonchoi deleted the fix-tests branch May 18, 2024 18:51
Arindam200 pushed a commit that referenced this pull request Aug 16, 2024
…etPrefix (vercel#68694)

This PR fixes two issues with the use of `assetPrefix`:

#1: vercel#64710
`assetPrefix` needs to be handled in `dev`, `deploy`, and `start`. In
the current approach, only `dev` and `start` were handled, but a quirk
of the implementation caused rewrites for non-asset paths to not be able
to be used in `afterFiles` rewrites.

#2: When deploying Next.js (such as on Vercel), you need to add your own
`beforeFiles` rewrite for `/${assetPrefix}/_next/...` requests or
otherwise they would 404.

This PR creates an automatically added `rewrite` to `beforeFiles` that
handles the case for `dev`, `start`, and `deploy`, removes the existing
logic in `filesystem.ts`, and adds more tests to check the behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant