The online environment url is modified when use publicPath
See original GitHub issueVersion
4.5.12
Reproduction link
https://github.com/minspy/bug-reproduction.git
Environment info
No specific environment required
Steps to reproduce
- npm run develop
- run in live server
What is expected?
do not modify the url
What is actually happening?
the url is modified when build and run in server
Issue Analytics
- State:
- Created 2 years ago
- Comments:7
Top Results From Across the Web
Webpack5 Automatic publicPath is not supported in this browser
The error is caused by a bug in mini-css-extract-plugin 1.3.8 and lower in combination with Webpack 5. It is triggered when a stylesheet ......
Read more >Public Path - webpack
It allows you to specify the base path for all the assets within your application. Use Cases. There are a few use cases...
Read more >How to fix the Whitescreen After a Static Deployment with ...
The way how create-react-app has it's webpack configuration set up, this will replace the publicPath with the correct base URL for your app....
Read more >The build Property - Nuxt
The build property. Nuxt lets you customize the webpack configuration for building your web application as you want. analyze. Nuxt use webpack-bundle- ...
Read more >Webpack — Understanding the 'publicPath' mystery - Medium
Further, we can use webpack's publicPath to config wepack-dev-server to generate the bundled output files at some virtual location and not ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I used Charles as an agent to debug locally, it’s not worked and i have to demote vue3 to vue2 and it’s fixed self. I still think it’s a bug.
Please update your js in CDN. The code in your CDN is still using publicPath to create route.