-
Notifications
You must be signed in to change notification settings - Fork 370
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: add the user-defined output.assetPrefix
config for the node mode of modern deploy
#6075
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: a5295cb The changes in this PR will be included in the next version bump. This PR includes changesets to release 280 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for modernjs-byted ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Thank you for your PR. Have you encountered this problem in a real project before? Because Modern.js will serialize the |
Summary
When using
modern deploy
, the project's configuredoutput.assetPrefix
is ignored, which results in static resource files failing to be accessed in the Node.js deployment mode.For example, if the user configures
assetPrefix
as/foo
, the URLs for the generated static resource files will start with/foo/static
. However, if this configuration is ignored in the generated.output/index.js
, the production server will continue to expect static resources to be prefixed with/static
, leading to failures in accessing the static resource files.Checklist
pnpm run change
.