production build issue `Uncaught Error: No NgModule metadata found for 't'.` about universal

[fulls1z3]

@ChrisDalley after upgrading to Node.js v8 and TypeScript v2.4.1 I'm also getting errors, however they're connected with rxjs.

The reason that the production builds resulting with failure is because the no-errors webpack plugin (prevents the build to be complete in case of any errors).

I'm currently working on a breaking change for the webpack configuration, and I think we'll find a solution to these issues. Meanwhile ping me when you face something useful.

[fulls1z3]

@ChrisDalley I edited the post, @ngtools/webpack appears now 😄

[fulls1z3]

@ChrisDalley this has been solved using the latest @ngtools/webpack.

[fulls1z3]

@ChrisDalley now I reproduced this error, I think things will become easier now 👍

[fulls1z3]

@ChrisDalley can you please share the exact @angular, typescript, @ngtools/webpack and rxjs versions? That might be useful.

[fulls1z3]

@ChrisDalley I'll also need the exact webpack version that you're using.

[ChrisDalley]

@fulls1z3 Here are the versions
@ angular/[email protected]
[email protected]
[email protected]
[email protected]

[fulls1z3]

@ChrisDalley I found it! It's all about @ngtools/webpack. Please let me know which version of @ngtools/webpack is at your system (better have a check looking at the package.json in the node_modules folder). Meanwhile, I'll try to find out the maximum working version of @ngtools/webpack.

[ChrisDalley]

@fulls1z3 - Thanks for taking a look so fast! Its all about what package though sorry? It didnt show in your last message!

[ChrisDalley]

Oh great! Im currently on version

@ngtools/[email protected]

[fulls1z3]

Try to switch to v1.3.3 now if things are urgent. Further versions do not work. I'm not surprised, @angular/cli still seems unreliable.

I'll update the repo within a few hours if things are not urgent for you. For now, use this dude:

package.json

"@ngtools/webpack": "1.3.3",

[ChrisDalley]

@fulls1z3 thats done the job - cheers for the help! Great work with the repo btw 😄

[fulls1z3]

@ChrisDalley thanks too, and it would be nice if you can make a favor: Can you please post this issue (meanwhile I'm working for a permanent solution over here), with same details at the @angular/cli repository - mentioning @ngtools/webpack with working and non-working versions?

It would definitely help the Angular team to reconsider their strategy and solve this issue on the upcoming releases of @ngtools/webpack. you can refer to this issue and my name too, no problem.

Cheers 👍

[ChrisDalley]

@fulls1z3 - Thanks for the update :)