Angular-CLI/Webpack Compiling Error
See original GitHub issueGetting an error when compiling with Angular-CLI
ERROR in Error encountered resolving symbol values statically. Calling function 'InjectionToken', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol HotkeyOptions in /Users/username/git/foo/node_modules/angular2-hotkeys/src/hotkey.options.d.ts, resolving symbol HotkeyModule.forRoot in /Users/username/git/foo/node_modules/angular2-hotkeys/index.d.ts, resolving symbol AppModule in /Users/username/git/foo/src/app/app.module.ts, resolving symbol AppModule in /Users/username/git/foo/src/app/app.module.ts
webpack: Failed to compile.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Angular: ng serve gives "webpack: Failed to compile"
This is a bug, caused by the folder whose name starts with an exclamation mark in the path to the project:
Read more >Web pack failed to compile · Issue #13799 · angular/angular-cli
ERROR in Could not resolve module...... Command. ng build; ng serve. Description. I cloned working angular 4 project.
Read more >Angular compiler options
See troubleshooting template errors. When you use the Angular CLI command ng new --strict , it is set to true in the new...
Read more >Angular - Code with Mosh Forum
Hello guys, I am having this error for 2 days now and I can't find a ... Error: Failed to initialize Angular compilation...
Read more >Angular 4webpack: Failed to compile. when start the app (i.e ...
I would upgrade all dependencies to their latest versions. remove node_modules and npm install again. Regards Sander.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You must stay on the 1.x.x version if you’re using angular 2.x.x. Only switch to the 2.x.x versions of you are using angular beta.4. (check the github release tags for the current versions of this project). That issue though is unrelated to the reported one.
v1.0.3 worked for me. ie: