It is an npm 5.4.0 issue https://github.com/npm/npm/issues/18287 Workarounds are downgrade to 5.3 try running with –no-optional, i.e. npm install –no-optional
The npm update –dd output says why at the end: …not updating @angular/common because it’s currently at the maximum version that matches its specified semver range Look at this specific package, angular/common. You have it set to 2.0.0, which means npm will always fetch that specific version. If you want the package to update, you need to use a semver … Read more
Verify that you have the latest version of Node.js installed (or, at least 13.2.0+). Then do one of the following, as described in the documentation: Option 1 In the nearest parent package.json file, add the top-level “type” field with a value of “module”. This will ensure that all .js and .mjs files are interpreted as ES modules. You can interpret individual files as CommonJS by using the .cjs extension. … Read more
Turned out to be an issue with Webpack just not resolving an import – talk about horrible horrible error messages 🙁
Using npm, I followed the getting started directions on the Angular CLI quick start page. Angular CLI Quickstart Running ng serve –open after creating and going into my new project “frontend” gave this error: I have tried suggestions from the other question similar to mine but it did not work. Answer was to run npm … Read more
It looks like you might not have defined a start script in your package.json file or your project does not contain a server.js file. If there is a server.js file in the root of your package, then npm will default the start command to node server.js. You could either change the name of your application script to server.js or add the following to … Read more