We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello Zaid, thank's for your great repository.
In order to allow the refresh in webpack on a url in history mode, we can set the following property in the devServer:
devServer: { publicPath: "/", contentBase: resolve(CONFIG.assetsDir), port: CONFIG.devServerPort, proxy: CONFIG.devServerProxy, hot: true, inline: true, historyApiFallback: true // <===== }
ref.: https://webpack.js.org/configuration/dev-server/#devserverhistoryapifallback
This allow to not have the 404 error message and also allow refresh (F5). I prefer the history mode to hashes.
In such case, we might also want to add in the index.html the following:
<base href="/" target="_blank">
This will find the JS at the root path (note that it can also be injected using webpack, but I guess it's to the developer to know that).
The text was updated successfully, but these errors were encountered:
Awesome stuff @Nordes, I will make sure to add these comments in the docs about pathMode routing. Thanks a lot 🙏
Sorry, something went wrong.
No branches or pull requests
Hello Zaid, thank's for your great repository.
In order to allow the refresh in webpack on a url in history mode, we can set the following property in the devServer:
ref.: https://webpack.js.org/configuration/dev-server/#devserverhistoryapifallback
This allow to not have the 404 error message and also allow refresh (F5). I prefer the history mode to hashes.
In such case, we might also want to add in the index.html the following:
This will find the JS at the root path (note that it can also be injected using webpack, but I guess it's to the developer to know that).
The text was updated successfully, but these errors were encountered: