-
Notifications
You must be signed in to change notification settings - Fork 12
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
Cannot see generated files in dev-server #7
Comments
After some try/fail/repeat I found out that setting
works. Also // Prefix for file names (html will be container icons with this prefix)
prefix: `${globals.publicPath}icons/`,
// Output path for icons (icons will be saved to output.path(webpack config) + this key)
output: './icons/' works (with globals.publicPath ending in '/'). Using hash:8 screws up everything since it's not supported in Other settings do not work for me, because of a MemoryFileSystem EACCESS permission denied error 😕 which I found out using Hope this helps fixing bugs (if any) or other people struggling against similar issues. |
Thanks, that helps. You can still use the hash for production builds like this:
|
Using output: './' in dev-server works perfectly for the root path, e.g. http://localhost:port/ But when you navigate to a deeper path in your website, you'll unfortunately get a 404 error, since it will be relative to the current path. My webpack output.publicPath is '/', so I'm not sure what to do to make this work 100% both in development and production. |
Hi there,
I'm using this plugin together with HtmlWebpackPlugin and HtmlWebpackTemplate
It works fine while bundling, i.e. generating the folders with the icons and the rest. However when using the dev server such files are emitted but are not created, i.e. when browsing the
http://localhost:<port>/webpack-dev-server
URL I cannot see the folder with the icons listed and when the browser requests, for instance, a favicon, I get a 404:http://localhost:<port>/icons-<hash>/favicon.ico
response: Cannot GET /icons-1a4ee607/favicon.ico
This is a bit annoying when developing. How can I check if I'm doing something wrong? Or is this just a bug?
Al plugins are latest versions and so is webpack
Configuration
globals.publicPath
is '/' in dev-server mode in my setup.The text was updated successfully, but these errors were encountered: