-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not find a declaration file for module AppModuleNgFactory #149
Comments
Have you installed the npm packages? cmd:
Greetings Damien |
Hi Damien, I use yarn and I installed the next packages (using yarn install): Thanks, |
Sorry, issue closed by my mistake :( I mean, it's still opened |
Hi guys, any other suggestions? Thanks, |
I really can not reproduce this :( Hmm... did you make changes to the repo? In the meantime it was updated to 6.1.0 - Do you still have the issues? For me Cheers |
Hi guys! I run npm install && npm run build-production but when I'm trying to build the solution I have the same issue in visual studio... Any ideas? Thanks. |
Hi all,
After updating to Angular 6 I have an error with exporting AppModuleNgFactory in main-aot.ts while running build-production:
ERROR in [at-loader] ./angularApp/main-aot.ts:7:36
TS7016: Could not find a declaration file for module './app/app.module.ngfactory'. 'D:/.. app.module.ngfactory.js' implicitly has an 'any' type.
Child html-webpack-plugin for "index.html":
[0] ./~/html-webpack-plugin/lib/loader.js!./angularApp/index.html 627 bytes {0} [built]
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] webpack-production:
set NODE_ENV=production && webpack
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] webpack-production 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:
...
error Command failed with exit code 2.
My main-aot.ts:
What do you think what fix could be applied here? Thanks.
The text was updated successfully, but these errors were encountered: