NPM START Hangs with Webpack: Wait Until Bundle Finished
See original GitHub issue-
I’m submitting a … [* ] bug report [ ] feature request [ ] question about the decisions made in the repository
-
Do you want to request a feature or report a bug?
-
What is the current behavior?
It seems that https://github.com/akveo/ng2-admin/issues/723 has arbitrarily returned. Issue disappeared after I pulled the latest master 3 days ago as suggested. The only change I made before it stopped working again was to “rm -rf node_modules” and “npm install”. After that “npm start” started to hang again. It’s not always at the same percent/file, but it seems to always be around 46-48%.
As mentioned in the previous report, commenting out the @import’s in /src/theme/initial.scss allows the “npm start” to proceed, but I had not done that previously to resolve the issue (I just pulled the latest master as suggested). Also, I’m not sure what the side-effects might be of commenting out those style imports.
Output:
$ npm start
> ng2-admin@0.9.0 start C:\Users\dave.pollastrini\git\ng2-admin
> npm run server:dev
> ng2-admin@0.9.0 server:dev C:\Users\dave.pollastrini\git\ng2-admin
> webpack-dev-server --config config/webpack.dev.js --progress --profile --watch --content-base src/
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
fallbackLoader option has been deprecated - replace with "fallback"
loader option has been deprecated - replace with "use"
DLL: Checking if DLLs are valid.
DLL: All DLLs are valid.
Project is running at http://localhost:3000/
webpack output is served from /
Content not from webpack is served from C:\Users\dave.pollastrini\git\ng2-admin\src
404s will fallback to /index.html
10% building modules 6/12 modules 6 active ...n\node_modules\webpack\hot\emitter.js
[at-loader] Using typescript@2.1.6 from typescript and "tsconfig.json" from C:\Users\dave.pollastrini\git\ng2-admin\tsconfig.webpack.json (in a forked process).
47% building modules 314/326 modules 12 active ...min\src\app\theme\validators\index.tswebpack: wait until bundle finished: /
webpack: wait until bundle finished: /
webpack: wait until bundle finished: /
webpack: wait until bundle finished: /
-
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
-
What is the expected behavior?
-
What is the motivation / use case for changing the behavior?
-
Please tell us about your environment:
- Angular version: 2.0.0-rc.X
- Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
- Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
Issue Analytics
- State:
- Created 7 years ago
- Comments:10
Top Related StackOverflow Question
Could you guys try doing the following:
and let us know how it goes.
Thanks.
replace sass-loader with version 6.0.3 and delete version 4.1.1 files in node_modules ,that’s work for me