Closed
Description
Do you want to request a feature or report a bug? Bug
What is the current behavior?
https://travis-ci.org/julmot/form-components/builds/346048668#L4063-L4081
If the current behavior is a bug, please provide the steps to reproduce.
Run the build of this repository which uses these settings. PR: julkue/form-components#9
What is the expected behavior?
It shouldn't fail or provide a meaningful message that helps resolving the issue. The current message looks like an internal error.
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
webpack v4
Win10
node v6.11.3
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
sokra commentedon Feb 26, 2018
Did you upgrade the extract-text-webpack-plugin to latest version?
julkue commentedon Feb 26, 2018
@sokra To which version? I'm using v3.0.2 which is -- according to this page -- the latest available stable version. So from my point of view, yes, I'm using the latest version.
fyi: I've just updated the PR to set the version explicitly, see https://github.com/julmot/form-components/pull/9/files#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R38
Dirtyburger1338 commentedon Feb 26, 2018
Just got the same issue directly after installing webpack
webpack 4.0.0
node 8.9.3
text-webpack-plugin 3.0.2
chrste90 commentedon Feb 26, 2018
I think you have to install
v4.0.0-alpha.0of text-webpack-plugin.As you can see in the release notes under Code Refactoring:
ExtractTextPlugin: update to new plugin system and API's.julkue commentedon Feb 26, 2018
Can't imagine that relaying on alpha releases is intended. (haven't checked if it works)
Dirtyburger1338 commentedon Feb 26, 2018
using v4.0.0-alpha.0 worked for me
julkue commentedon Feb 26, 2018
@sokra If using v4.0.0-alpha.0 works (can't confirm currently), is this the way to go?
rgbkrk commentedon Feb 27, 2018
I'm no longer using
extract-text-webpack-pluginanywhere, is there a way to find out which plugin is generating this warning?sokra commentedon Feb 27, 2018
node --trace-depracationhoqqun commentedon Feb 27, 2018
I had the same problem.but resolved it using version 3.11.0
julkue commentedon Feb 27, 2018
@sokra What's the solution in this regard?
montogeek commentedon Feb 27, 2018
@julmot Try with
extract-text-webpack-plugin@nextyinsang commentedon Feb 28, 2018
extract-text-webpack-plugin
npm i -D extract-text-webpack-plugin@nextAlejandraCP commentedon Feb 28, 2018
Works with v4.0.0-alpha.0
zhy023 commentedon Feb 28, 2018
No Works with extract-text-webpack-plugin v4.0.0-beta.0
61 remaining items