Skip to content
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 init trying to use unsupported extract-text-webpack-plugin #320

Closed
chrispickford opened this issue Mar 8, 2018 · 4 comments
Closed

Comments

@chrispickford
Copy link

chrispickford commented Mar 8, 2018

Type: Bug

What is the current behavior?

Repro steps here: https://stackoverflow.com/questions/49172495/webpack-init-trying-to-use-unsupported-extract-text-webpack-plugin

  1. dotnew new web
  2. yarn init
  3. yarn add --dev webpack webpack-cli
  4. webpack init
  5. webpack

Displays the following error message:

(node:19320) DeprecationWarning: Tapable.plugin is deprecated. Use new
API on '.hooks' instead
D:\SRC\MISC\WebpackTest\node_modules\webpack\lib\Chunk.js:460
throw new Error(
^

Error: Chunk.entrypoints: Use Chunks.groupsIterable and filter by
instanceof Entrypoint instead
at Chunk.get (D:\SRC\MISC\WebpackTest\node_modules\webpack\lib\Chunk.js:460:9)
at D:\SRC\MISC\WebpackTest\node_modules\extract-text-webpack-plugin\dist\index.js:176:48
at Array.forEach ()
at D:\SRC\MISC\WebpackTest\node_modules\extract-text-webpack-plugin\dist\index.js:171:18
at AsyncSeriesHook.eval [as callAsync] (eval at create (D:\SRC\MISC\WebpackTest\node_modules\tapable\lib\HookCodeFactory.js:24:12),
:7:1)
at AsyncSeriesHook.lazyCompileHook [as _callAsync] (D:\SRC\MISC\WebpackTest\node_modules\tapable\lib\Hook.js:35:21)
at Compilation.seal (D:\SRC\MISC\WebpackTest\node_modules\webpack\lib\Compilation.js:881:27)
at hooks.make.callAsync.err (D:\SRC\MISC\WebpackTest\node_modules\webpack\lib\Compiler.js:464:17)
at _err0 (eval at create (D:\SRC\MISC\WebpackTest\node_modules\tapable\lib\HookCodeFactory.js:24:12),
:11:1)
at _addModuleChain (D:\SRC\MISC\WebpackTest\node_modules\webpack\lib\Compilation.js:749:12)
at processModuleDependencies.err (D:\SRC\MISC\WebpackTest\node_modules\webpack\lib\Compilation.js:688:9)
at process._tickCallback (internal/process/next_tick.js:150:11)

What is the expected behavior?

A freshly initialised project configuration should not throw errors upon build.

@jamsoft
Copy link

jamsoft commented Mar 8, 2018

I can confirm that I've reproduced this issue.

@montogeek
Copy link
Member

We need to use the new version, I could pick this one

@evenstensberg
Copy link
Member

yes

@evenstensberg
Copy link
Member

Fixed in #323

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants