jeudi 2 août 2018

Error: Chunk.entrypoints: Use Chunks.groupsIterable and filter by instanceof Entrypoint instead

Getting this error When I am run the Script "npm run watch"

cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --config=node_modules/laravel-mix/setup/webpack.config.js

i 「webpack」: Watching enabled \ Building Modules (16%)C:\xampp\htdocs\VidhiStage\node_modules\webpack\lib\Chunk.js:824 throw new Error( ^

Error: Chunk.entrypoints: Use Chunks.groupsIterable and filter by instanceof Entrypoint instead at Chunk.get (C:\xampp\htdocs\VidhiStage\node_modules\webpack\lib\Chunk.js:824:9) at C:\xampp\htdocs\VidhiStage\node_modules\laravel-mix\node_modules\extract-text-webpack-plugin\dist\index.js:176:48 at Array.forEach () at C:\xampp\htdocs\VidhiStage\node_modules\laravel-mix\node_modules\extract-text-webpack-plugin\dist\index.js:171:18 at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\xampp\htdocs\VidhiStage\node_modules\tapable\lib\HookCodeFactory.js:24:12), :12:1) at AsyncSeriesHook.lazyCompileHook [as _callAsync] (C:\xampp\htdocs\VidhiStage\node_modules\tapable\lib\Hook.js:35:21) at Compilation.seal (C:\xampp\htdocs\VidhiStage\node_modules\webpack\lib\Compilation.js:1203:27) at hooks.make.callAsync.err (C:\xampp\htdocs\VidhiStage\node_modules\webpack\lib\Compiler.js:547:17) at _err0 (eval at create (C:\xampp\htdocs\VidhiStage\node_modules\tapable\lib\HookCodeFactory.js:24:12), :11:1) at _addModuleChain (C:\xampp\htdocs\VidhiStage\node_modules\webpack\lib\Compilation.js:1054:12) at processModuleDependencies.err (C:\xampp\htdocs\VidhiStage\node_modules\webpack\lib\Compilation.js:980:9) at process._tickCallback (internal/process/next_tick.js:172:11) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! VidhiStage@1.0.0 watch: cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --config=node_modules/laravel-mix/setup/webpack.config.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the VidhiStage@1.0.0 watch script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\BIKI MALLIK\AppData\Roaming\npm-cache_logs\2018-08-02T08_45_14_967Z-debug.log



via Chebli Mohamed

Aucun commentaire:

Enregistrer un commentaire