With the latest CLI, inside angular.json “test”: { “builder”: “@angular-devkit/build-angular:karma”, “options”: { “main”: “src/test.ts”, “polyfills”: “src/polyfills.ts”, “tsConfig”: “src/tsconfig.spec.json”, “karmaConfig”: “./karma.conf.js”, “codeCoverageExclude”: [“src/testing/**/*”],
Per this comment, you can add your application source via paths in tsconfig.json: { “compilerOptions”: { …, “baseUrl”: “.”, “paths”: { …, “@app/*”: [“app/*”], “@components/*”: [“components/*”] } } } Then you can import absolutely from app/ or components/ instead of relative to the current file: import {TextInputConfiguration} from “@components/configurations”; Note: baseUrl must be specified if … Read more
It turned out that you need to remove this line from “include” “src/**/*.ts” from tsconfig.app.json and only keep entry points in files (main.ts and polyfills.ts)
Update For Angular 11 I strongly recommend you to take a look at implementation with Webpack 5 Module Federation 🎉 https://github.com/alexzuza/angular-plugin-architecture-with-module-federation Previos version 🛠️ Github demo angular-plugin-architecture Maybe Ivy can change something but for the time being I use the solution that uses Angular CLI Custom Builder and meets the following requirements: AOT avoid duplicate … Read more
For Angular 6.1+ , you can use default pipe keyvalue ( Do review and upvote also ) : <ul> <li *ngFor=”let recipient of map | keyvalue”> {{recipient.key}} –> {{recipient.value}} </li> </ul> WORKING DEMO For the previous version : One simple solution to this is convert map to array : Array.from Component Side : map = … Read more
The ng g component plainsight/some-name makes a new directory when we use it. The final output will be: plainsight/some-name/some-name.component.ts To avoid that, make use of the flat option ng g component plainsight/some-name –flat and it will generate the files without making a new folder plainsight/some-name.component.ts
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
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
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
npm start will run whatever you have defined for the start command of the scripts object in your package.json file. So if it looks like this: “scripts”: { “start”: “ng serve” } Then npm start will run ng serve.