Thanks, Sander. Removing the the yarn.lock files and then removing all of the node_modules, following by "npm install" didn't solve the problem in my case but I do appreciate your suggestion.
Robert On Sunday, May 28, 2017 at 8:36:40 PM UTC-7, Sander Elias wrote: > > Hi Robert, > > I had something similar to this. In my case, I had to remove the yarn.lock > file, and remove my node_modules. (followed by a new install) > Often this is a mess up off the package manager (npm/yarn) you are using. > > 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.
