-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Full static payload.js not using publicPath #7923
Comments
I can confirm it's also not working for me. Every other resource does use the publicPath correctly. |
It's not working for me too. |
Same problem |
+1, same problem |
Thanks for your contribution to Nuxt.js!
Issues that are labeled as |
we are seeing this issue in @nathancall there's a patch release version of nuxt that might be worth trying to see if it resolves this issue. otherwise we might need to open a PR and patch nuxt ourselves. |
This should be fixed in v2.14.8. Please reopen if not. |
Versions
Reproduction
nuxt.config.js below in Additional Details.
Additional Details
Steps to reproduce
publicPath
in nuxt.config.js for a full static appnuxt generate
/dist/
directory to static hosting (S3 in this case)payload.js
fileWhat is Expected?
I would expect the
payload.js
file to also use the specifiedpublicPath
instead of using a relative path. I added apublicPath
specifically because I need absolute paths for everything.What is actually happening?
The
payload.js
files are being linked using relative paths. Bootstrap Vue actions (such as opening modals) are not functioning when deployed. I'm guessing it's related to this.runtime.js
(correct):https://khn.s3.us-east-1.amazonaws.com/virtual-series/runtime.ad4e919.js
payload.js
(incorrect):/static/1597456812/<page-filename>/payload.js
All other assets are using the
publicPath
as expected. Am I missing something?The text was updated successfully, but these errors were encountered: