-
-
Notifications
You must be signed in to change notification settings - Fork 381
support webpack v4 #264
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
support webpack v4 #264
Conversation
upgrade to new tapable hooks API
|
@mattkrick thanks for the PR, but you'll need to restore the PR template and properly fill in the details before we can review this. also looks like you have a failure in Travis CI you'll have to fix to move forward. |
|
@mattkrick friendly ping |
|
Something to mention about Previously: Watching {
startTime: 1519735902177,With webpack 4: Compiler {
_pluginCompat: |
|
Fucking A - I absolutely loathe how little documentation there is for this release. Thanks for the heads up @pi0 🍺 |
| context.rebuild = rebuild; | ||
| context.compiler.plugin('invalid', invalid); | ||
| context.compiler.plugin('run', invalid); | ||
| context.compiler.hooks.invalid.tap({name: 'CopyPlugin'}, invalid) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe all the names should be 'webpack-dev-middleware', not 'CopyPlugin'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed
|
Since the OP closed this, we'll be putting together a major release today for webpack@4 support. |
upgrade to new tapable hooks API
Summary
deprecation warnings appear if using the old API
Does this PR introduce a breaking change?
yes,webpack v4 only