Angular 5.2.7: No Provider for NgZone
See original GitHub issueI get the following error and i can’t figure out why:
FileDropComponent.html:2 ERROR Error: StaticInjectorError(AppModule)[FileComponent -> NgZone]: StaticInjectorError(Platform: core)[FileComponent -> NgZone]: NullInjectorError: No provider for NgZone! at _NullInjector.get (core.js:1002) at resolveToken (core.js:1300) at tryResolveToken (core.js:1242) at StaticInjector.get (core.js:1110) at resolveToken (core.js:1300) at tryResolveToken (core.js:1242) at StaticInjector.get (core.js:1110) at resolveNgModuleDep (core.js:10854) at NgModuleRef_.get (core.js:12087) at resolveDep (core.js:12577)
dependencies:
"@angular/animations": "^5.2.0", "@angular/common": "^5.2.0", "@angular/compiler": "^5.2.0", "@angular/core": "^5.2.0", "@angular/forms": "^5.2.0", "@angular/http": "^5.2.0", "@angular/platform-browser": "^5.2.0", "@angular/platform-browser-dynamic": "^5.2.0", "@angular/router": "^5.2.0", "core-js": "^2.4.1", "ngx-file-drop": "^2.0.5", "primeng": "^5.2.0", "rxjs": "^5.5.6", "zone.js": "^0.8.19"
Angular version: 5.2.7
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (7 by maintainers)

Top Related StackOverflow Question
For information, I had the same issue here. I’m using webpack as @jacobbutton to compile my project. Delete manually the node_modules folder from the ngx-file-drop directory works locally, but it’s not a suitable solution in our devops context… I’ve updaded angular from 5.1 to 5.2 (following this instructions : https://angular-update-guide.firebaseapp.com/) and it works fine now. Thanks for your works !
I’ve been having the same error for about the past few weeks after upgrading angular. I think there’s a conflict between my applications angular version and the angular version of ngx-file-drop.
The work around I’ve been using so far is removing ngx-file-drop’s node_modules folder before running webpack and compiling my application.