Hi Gunnar

But it is more important for me to get an idea about the risk to invest a 
> lot of time and money using Angular 7 as basis for my next project - and if 
> possible risks can be properly managed or mitigated. 
>
All projects that use build-tools are prone to this kind of issues. This is 
actually not unique to Angular.

arned now that Angular projects could get into a state where the production 
> build can fail while insufficient information about the reason is provided. 
>
Again, this is not unique to Angular, I have seen this happening to all 
sorts of projects. Especially when the original creator/maintainer has 
left. I think the risk with Angular is lower as for an average project.

If I understand you correcly, according to your experience this is not a 
> fatal risk and issues with the compilation for production could so far 
> always be solved with low costs, correct?  
>
Your problem (while not unique) is very rare. And yes. it can be repaired 
at low costs.

And how would you approach such an issue? Can the compilation process be 
> debugged or traced?
>
Yes, the compilation process can be debugged and logged. I have done this. 
However, that is not something I would recommend.
What I would recommend, is start a fresh project, and copy in module for 
module, until you find the culprit. It is a bit of a drag, but this way you 
can figure out the cause of your issue quickly.
Also, if it’s a corrupted tool-chain this will fix it in itself.

BTW, you said you did the rm -fr node_modules yarn install cycle. But are 
you sure you removed your yarn.lock package-lock.json files?
One of the problems I once had in a project was that files in my yarn cache 
where damaged. so that cycle would pull in a corrupted dep.

Sadly this kind of problem is something a developer has to deal with. I 
have seen it in all kind of projects.
As soon as there are 3rth party tools and any kind of package manager, this 
will happen. Not unique to Angular, or even Javascript.

Regards
Sander
​

-- 
You received this message because you are subscribed to the Google Groups 
"Angular and AngularJS discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to