The solution worked for me was ng serve –port 4401 (You can change 4401 to whatever number you want) Then launch browser -> http://localhost:4401/ Basically, I was having two Applications and with the help of the above approach now I am able to run both of them simultaneously in my development environment.
See Angular – Configure Environment Specific Defaults EDIT:- As predicted, GitHub Issue After the release of Angular CLI 15.1, a generation schematic will be available to add environment files for all existing build configurations within a project. Example usage: ng g environments To manually create: If you want to recreate environments, follow these steps: Create … Read more
The first path in the path variable needs to be the NPM path. Opening the Node.js command prompt I found that the ng command worked there. I dug into the shortcut and found that it references a command to ensure the first Path variable is NPM. To Fix: Right Clicked on My Computer (windows) Selected … Read more
As already said, angular library now support assets since the v9.x of angular. But it isn’t well explained on their website. To make it work you’ll have to: Add an assets folder at the root of your library project Add “assets”: [“./assets”], into the ng-package.json file of the library { “$schema”: “../../node_modules/ng-packagr/ng-package.schema.json”, “dest”: “../../dist/icon”, “assets”: … Read more
Thanks to this documentation link : https://www.typescriptlang.org/docs/handbook/triple-slash-directives.html [Angular 6+] You only have to add this line at the beginning (meaning line 1, with nothing before) of your Typescript file : /// <reference types=”@types/googlemaps” /> [Angular 5-] You only have to add this line anywhere in your Typescript file imports : import {} from “googlemaps”; Thanks … Read more
The problem (as outlined in typescript getting error TS2304: cannot find name ‘ require’) is that the type definitions for node are not installed. With a projected genned with @angular/cli 1.x, the specific steps should be: Step 1: Install @types/node with either of the following: – npm install –save @types/node – yarn add @types/node -D … Read more
To answer one of the questions, it is necessary to have both a global and local install for the tools to work. If you try to run ng serve on an application without the local install of the CLI (global install only), you will get the following error. You have to be inside an Angular … Read more
Install @angular-devkit/build-angular as dev dependency. This package is newly introduced in Angular 6.0 npm install –save-dev @angular-devkit/build-angular or, yarn add @angular-devkit/build-angular –dev
NEW ANSWER My experience of 15 hours has taught me that trying to serve an Angular app with Express during development is NOT a good idea. The proper way is to run Angular and Express as two different apps on two different ports. Angular will be served on port 4200 and Express on port 3000 … Read more
To answer your question, let’s assume that you are interested in a specific angular version and NOT in a specific angular-cli version (angular-cli is just a tool after all). A reasonnable move is to keep your angular-cli version alligned with your angular version, otherwise you risk to stumble into incompatibilities issues. So getting the correct … Read more