angular-cli-v6

I'm writing an Angular 6 Library and cannot figure out how to step into the typescript. I generated the app using: ng new mylibapp I then added the library using: ng g library @abc/cool-lib -p abc when I perform: ng build @abc/cool-lib it generates the code in the mylibapp/dist/abc/cool-lib folder How can I now debug this code and set breakpoints in the ts file located at mylibapp/projects/abc/cool-lib/src/lib Looking at the Angular CLI docs on libraries , it mentions the following: Some similar setups instead add the path to the source code directly inside tsconfig. This makes seeing changes

I am trying to turn off sourcemaps for my tests in Angular 6. I know the sourcemaps switch has been removed, e.g., ng test --sourcemaps=false . I have tried modifying my tsconfig file: { "extends": "../tsconfig.json", "compilerOptions": { ... "sourceMap": false }, as referenced by the angular.json test->configuration block: "test": { ... "options": { ... "tsConfig": "src/tsconfig.spec.json", The source maps are still being generated. You can use CLI v6.0.8 and above --source-map=false CLI v6.x --sourceMap=false CLI v1.x --sourcemaps=false Angular CLI changing this param from version to version

My npm version is 5.5.1 and angular cli version is 6.2.1 . When I try to create a new project using the command ng new Project_name then it is creating the latest version of angular (in my case it is creating Angular version ^6.1.0 ). But I want Angular4 . My question is how to create this Angualr2/4/5 (specific version instead of the latest version)? I don't think changing the version value in package.json will help in my case because there are some differences in the older versions and the latest 6 version (like the name of one file has been changed from angular-cli.json to anguar.json and

There are two sub-questions: Should I put secret environment variables in environment.ts file? The process variable shim is gone. If I use it, tsc will throw an error: Cannot find name 'process' . Here is my thing: About Q1: I don't think put secret environment variables in environment.ts file is correct. Because these files will be a push to source code management, like GitHub, gitlab, bitbucket. It's not safe. So I think secret environment variables should be passed through process.env , like process.env.ACCESS_TOKEN , or, if use docker-compose, should put the secret environment variables in

Today, I updated my angular cli to the latest version and encountered an error that stops me from creating a new Angular project. Following is the error log that I get after executing ng new app-name : Error: Schematic "ng-new" not found in collection "@schematics/angular". at SchematicEngine.createSchematic (C:\Users\xyz\node_modules\@angular\cli\node_modules\@angular-devkit\schematics\src\engine\engine.js:155:23) at CollectionImpl.createSchematic (C:\Users\xyz\node_modules\@angular\cli\node_modules\@angular-devkit\schematics\src\engine\collection.js:12:29) at NodeWorkflow.execute (C:\Users

I want to use the Google Maps API with my Angular project, so I used these two commands to install npm packages: npm install @agm/core --save-dev npm install @types/googlemaps --save-dev I added this line to my component: import {} from "@types/googlemaps"; But I see these 2 errors in VS Code: [ts] File 'h:/Angular Projects/Breakfast/client/breakfast/node_modules/@types/googlemaps/index.d.ts' is not a module. [ts] Cannot import type declaration files. Consider importing 'googlemaps' instead of '@types/googlemaps'. I added these lines "types": ["googlemaps"] "moduleResolution": "node" to