I completely started from scratch. I believe the problem was that I didn't precisely upgrade *angular-cli* in the prescribed way. The proper way is as follows:
Global package: npm uninstall -g @angular/cli npm cache clean npm install -g @angular/cli@latest Local project package: rm -rf node_modules dist # use rmdir /S/Q node_modules dist in Windows Command Prompt; use rm -r -fo node_modules,dist in Windows PowerShell npm install --save-dev @angular/cli@latest npm install Also, a colleague pointed out that he had upgraded our project to Angular 4 so that was done previously. I'm now up & running again. Unfortunately the "Maximum call stack size exceeded" error was not resolved by this new version of Angular/CLI but we have strong reason to believe that this issue is due to circular references which we need to resolve. The "strange" way to solve this problem in Development mode is to simply re-save any file in your project, even if you don't change it. Unfortunately we're still blocked from generate the bundled files to deploy the app. Robert On Thursday, June 1, 2017 at 9:58:46 AM UTC-7, [email protected] wrote: > > To try to resolve a circular dependency issue with WebPack, I upgraded > Angular/CLI from 1.0 to 1.1. This didn't work right so I uninstalled > Angular altogether and reinstalled it. This upgraded me from Angular 2 to > Angular 4. > > I'm now dead in the water with messages about "Cannot find module > @angular/core" and "Cannot find module @angular/router". > > I've tried several things but am currently stuck. > > Anyone have any advice? > > Robert > > -- 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.
