-
Notifications
You must be signed in to change notification settings - Fork 511
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
Deployment to Cloudflare Pages broken with new Nuxt 3.8 app manifest feature #1844
Labels
Comments
manniL
added
bug
Something isn't working
preset:cloudflare
and removed
pending triage
labels
Oct 26, 2023
@atinux This was already mentioned in the posts' "Additional context", along with its downsides. Commenting the same again separately may lead to people incorrectly assuming it's a good long-term solution. |
8 tasks
@favna read too fast sorry about this, deleted the comment to avoid any downsides. |
The fix is released on nitro@2.7.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Darwin
v18.18.2
3.8.0
3.9.1
2.7.0
npm@9.8.1
-
nitro
-
-
Reproduction
https://github.com/AaronBeaudoin/nuxt-3-issue-1
Describe the bug
In Nuxt 3.8 a new feature was introduced which adds a new
/_nuxt/builds/meta/<buildId>.json
in the build output directory. This causes the following two new entries to be added tonitro.options.publicAssets
:The Cloudflare Pages preset then "copies" these over when generating a
_routes.json
file:This results in the following error during deployment:
I originally created nuxt/nuxt#23796 when I discovered this issue, but according to the maintainer who responded it is Nitro's responsibility to ensure that the overlapping URLs created in
nitro.options.publicAssets
are correctly handled when creating_routes.json
.Additional context
For now this issue can be avoided with
experimental: { appManifest: false }
innuxt.config.ts
. However, this issue will come back again if any other overlapping URLs ever make it intonitro.options.publicAssets
.Logs
No response
The text was updated successfully, but these errors were encountered: