-
-
Notifications
You must be signed in to change notification settings - Fork 282
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
[Feature] Provide default context
option
#148
Comments
The pattern.context isn't sufficient enough for you I guess? {
context: 'from/directory', // <= ?
from: '**/*',
to: '/absolute/path'
} Feel free to open a PR if you want to tackle this of course 😛 |
Right, all of my patterns are going to repeat the same context, so it'd be nice to just have it once (while allowing overrides, of course) |
cletusw
added a commit
to cletusw/copy-webpack-plugin
that referenced
this issue
Oct 5, 2017
Overrides webpack context, overridden by pattern context Fixed webpack-contrib#148
cletusw
added a commit
to cletusw/copy-webpack-plugin
that referenced
this issue
Oct 5, 2017
Overrides webpack context, overridden by pattern context Fixes webpack-contrib#148
@michael-ciniawsky Created #149 to add this option. |
cletusw
added a commit
to cletusw/copy-webpack-plugin
that referenced
this issue
Oct 5, 2017
Overrides webpack context, overridden by pattern context Fixes webpack-contrib#148
michael-ciniawsky
changed the title
Provide default
[Feature] Provide default Oct 5, 2017
context
optioncontext
option
@michael-ciniawsky Just added a comment. Not sure what the expected behavior is. |
cletusw
added a commit
to cletusw/copy-webpack-plugin
that referenced
this issue
Oct 19, 2017
Overrides webpack context, overridden by pattern context Fixes webpack-contrib#148
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently,
context
defaults tocompiler.options.context
from webpack. However, I'd like all my copy patterns to use./src
as the default context, even though I can't change my webpack context to that for other reasons.Could we add a fallback to the plugin options? The overall context fallback logic would be:
context
property on pattern object ->context
property in plugin options ->context
property on webpack configIf this sounds okay, I can try to come up with a PR.
The text was updated successfully, but these errors were encountered: