Michael Ciniawsky
Michael Ciniawsky
Maybe something in the direction of https://github.com/webpack-contrib/copy-webpack-plugin/pull/119 would be sufficient enough/in the meantime
``` cp src/* dist/* && webpack ``` Sry, this plugin is an **integration** of `cp` for webpack **during** runs, there is no way to start/use a `webpack` plugin without actually...
Sry, I overread `entrypoints` :), (maybe) possible, but not supported atm
@alex-mm What's the particular usecase for this in terms of development ? 😛
We could maybe include the filename as attribute, but I'm still not really convinced by the idea. If this is really wanted someone feel free/please open a PR for further...
Send PR for discussion how this would/could look like, but tbh I have no idea how `css-loader` should do that, since it works on a *per file* (chunk) basis like...
The conversion to ES2015 Modules will definitely by coming soon, but this is a joined effort with changes needed in `style-loader` && `extract-textwebpack-plugin` aswell + in the PR the author...
Can you please give a small example?
`this.resourcePath` should be the absolute path without anything webpack specific (`request`) ```js this.request = 'loader-1!loader-2!loader-n!./path/to/file?query' this.resource = 'path/to/file?query' this.resourcePath = 'path//to/file' this.resourceQuery = 'query' ``` Please post a before after...
Did you initially use `webpack =< v1.0.0` ? If I remember right there were changes to the Loader API between `v1.0.0` => `v2.0.0`