Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Compilation warnings upon app start

See original GitHub issue

I’m getting two warnings when starting an angular-cli app using the newest version of angular (5.0.5):

WARNING in ./node_modules/@chevtek/angular-spinners/node_modules/@angular/core/@angular/core.es5.js
5659:15-36 Critical dependency: the request of a dependency is an expression
    at ImportLazyContextDependency.getWarnings (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/dependencies/ContextDependency.js:39:18)
    at Compilation.reportDependencyErrorsAndWarnings (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/Compilation.js:703:24)
    at Compilation.finish (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/Compilation.js:561:9)
    at applyPluginsParallel.err (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/Compiler.js:506:17)
    at /Users/sdornan/Code/search-compare-ng2/node_modules/tapable/lib/Tapable.js:289:11
    at _addModuleChain (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/Compilation.js:507:11)
    at processModuleDependencies.err (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/Compilation.js:477:14)
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)
 @ ./node_modules/@chevtek/angular-spinners/node_modules/@angular/core/@angular/core.es5.js
 @ ./node_modules/@chevtek/angular-spinners/dist/src/spinner.module.js
 @ ./node_modules/@chevtek/angular-spinners/dist/src/index.js
 @ ./node_modules/@chevtek/angular-spinners/dist/index.js
 @ ./src/app/shared/shared.module.ts
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://0.0.0.0:0 ./src/main.ts

WARNING in ./node_modules/@chevtek/angular-spinners/node_modules/@angular/core/@angular/core.es5.js
5675:15-102 Critical dependency: the request of a dependency is an expression
    at ImportLazyContextDependency.getWarnings (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/dependencies/ContextDependency.js:39:18)
    at Compilation.reportDependencyErrorsAndWarnings (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/Compilation.js:703:24)
    at Compilation.finish (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/Compilation.js:561:9)
    at applyPluginsParallel.err (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/Compiler.js:506:17)
    at /Users/sdornan/Code/search-compare-ng2/node_modules/tapable/lib/Tapable.js:289:11
    at _addModuleChain (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/Compilation.js:507:11)
    at processModuleDependencies.err (/Users/sdornan/Code/search-compare-ng2/node_modules/webpack/lib/Compilation.js:477:14)
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)
 @ ./node_modules/@chevtek/angular-spinners/node_modules/@angular/core/@angular/core.es5.js
 @ ./node_modules/@chevtek/angular-spinners/dist/src/spinner.module.js
 @ ./node_modules/@chevtek/angular-spinners/dist/src/index.js
 @ ./node_modules/@chevtek/angular-spinners/dist/index.js
 @ ./src/app/shared/shared.module.ts
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://0.0.0.0:0 ./src/main.ts

webpack: Compiled with warnings.

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:9

Top GitHub Comments

1reaction

MariusRettlercommented, Jan 24, 2018

So i solved the problem by replacing this dependency with a fork of this project. I used this updated fork: https://github.com/JoeSong/angular-spinners Just do: npm install --save https://github.com/JoeSong/angular-spinners/master

maybe remove the node_modules folder and the package-lock.json first, then update the dependency and do an npm install. After that the warnings should be gone.

0reactions

frdrcklopezcommented, Jan 24, 2018