-
Notifications
You must be signed in to change notification settings - Fork 56
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
webpack plugin does not have access to output path when running webpack-dev-server program #1
Comments
Using v1.12.2 of webpack, which seems to be the latest. |
@frantic please raise this with https://github.com/webpack/webpack and CC me. I cannot see a reason why compiler.options.path is different from what you have defined in the webpack config. |
@gajus does this work for you? Can you |
I ran into the same problem, it seems to be due to the command line wrapper webpack-dev-server forcing the output path to / here. Commenting that bit out seems to fix it, so I just opted to skip the command line wrapper and use the API. I imagine this means it doesn't affect anyone using grunt, etc., either. |
This plugin will require that |
I have this issue too. Is it possible to switch to |
same problem |
Same problem here |
I might be late at the party but this issue is still happening with HtmlWebpackPlugin. See issue: HtmlWebpackPlugin Issue#384 Here are my depedencies version: |
Same problem here. Using webpack-dev-server 1.16.4. |
For some reason the plugin picks up a wrong output path for my file, instead of
./dist
I just get/
.My config:
but the plugin creates a file in my root -
/bundle.js
. I've added some logging. The config exported fromwebpack.config.js
looks like this:however inside plugin's
apply
when Iconsole.log(compiler.options);
I get:Is it a webpack's issue?
The text was updated successfully, but these errors were encountered: