CLI tool for Angular
Branch: master
Clone or download
alan-agius4 and kyliau fix(@schematics/angular): `findModuleFromOptions` not handling proper…
…ly different casing in name

At the moment users can have various casing and seperatirs in paths, we should not always dasherize the name when resolving modules.

As for example when providing something like:

```
/module/SubModule/feature
```

It won't be able to resolve the modules properly as `sub-module` does't exist.

This PR also updates the test for underscore as previously it was not properly testing this usercase, since the formatter was used on name and not th path.

Fixes #13714
Latest commit 9bf8b3e Feb 20, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.buildkite ci: add timeout and retry to Buildkite Jan 14, 2019
.circleci ci: add ivy snapshots CI job Feb 13, 2019
.github docs: new GitHub Issue templates (#13461) Jan 18, 2019
benchmark/aio build: workaround yarn tgz bug Sep 10, 2018
bin build: terminate process with non zero error code when build fails Jan 11, 2019
docs docs: update release process Jan 24, 2019
etc fix(@angular-devkit/core): fix true schemas post transform step Feb 19, 2019
lib test: downgrade output of typescript to es2016 for istanbul Dec 14, 2018
packages fix(@schematics/angular): `findModuleFromOptions` not handling proper… Feb 21, 2019
scripts build: fix invalid commits that made it through Feb 13, 2019
tests fix(@angular/cli): remove redundant typescript/compiler-cli compatibi… Feb 20, 2019
third_party refactor: use vendored supports-color Feb 19, 2019
tools build: update `quicktype-core` to generate camelCase acronyms Dec 11, 2018
.appveyor.yml ci: use puppeteer Jan 14, 2019
.bazelignore build: Use fine-grained node_module deps Nov 1, 2018
.bazelrc build: Use fine-grained node_module deps Nov 1, 2018
.editorconfig style: update editorconfig website url (#12923) Nov 14, 2018
.gitattributes style: add .gitattributes file (#13086) Nov 30, 2018
.gitignore ci: disable bazel in devkit-admin build Sep 13, 2018
.mailmap build: add Alan to the mailmap file Jan 18, 2019
.monorepo.json release: v8.0.0-beta.1 Feb 18, 2019
.nvmrc build: update nvmrc to use node 10 Sep 19, 2018
BUILD build: Use fine-grained node_module deps Nov 1, 2018
CONTRIBUTING.md docs: fix grammar error Jan 8, 2019
Dockerfile ci: use puppeteer Jan 14, 2019
LICENSE build: move devkit repo back to angular-cli Jun 6, 2018
README.md docs: change link for CLI readme to be relative Dec 6, 2018
WORKSPACE build: Update Bazel workspace Jan 17, 2019
appveyor-e2e.bat ci: add windows buildkite Jan 14, 2019
package.json feat(@angular-devkit/architect-cli): CLI tool to use new Architect API Feb 19, 2019
renovate.json ci: disable major `devDependencies` updates Dec 21, 2018
tsconfig-test.json build: Use fine-grained node_module deps Nov 1, 2018
tsconfig.json ci: add ts api guardian (#12010) Nov 30, 2018
tslint.json style: add comments in tslint.json Nov 14, 2018
yarn.lock build: update webpack-dev-middleware to version 3.6.0 Feb 20, 2019

README.md

Angular CLI

Development tools and libraries specialized for Angular

This is the home of the DevKit and the Angular CLI code. You can find the Angular CLI specific README here.

CircleCI branch Dependency Status devDependency Status

License

GitHub forks GitHub stars

Quick Links

Gitter Contributing Angular CLI

The Goal of Angular CLI

The Angular CLI creates, manages, builds and test your Angular projects. It's built on top of the Angular DevKit.

The Goal of DevKit

DevKit's goal is to provide a large set of libraries that can be used to manage, develop, deploy and analyze your code.

Getting Started - Local Development

Installation

To get started locally, follow these instructions:

  1. If you haven't done it already, make a fork of this repo.
  2. Clone to your local computer using git.
  3. Make sure that you have Node 10.9 or later installed. See instructions here. The Angular CLI requires Node 8, but development requires Node 10.
  4. Make sure that you have yarn installed; see instructions here.
  5. Run yarn (no arguments) from the root of your clone of this project.
  6. Run yarn link to add all custom scripts we use to your global install.

Creating New Packages

Adding a package to this repository means running two separate commands:

  1. schematics devkit:package PACKAGE_NAME. This will update the .monorepo file, and create the base files for the new package (package.json, src/index, etc).
  2. devkit-admin templates. This will update the README and all other template files that might have changed when adding a new package.

For private packages, you will need to add a "private": true key to your package.json manually. This will require re-running the template admin script.

Packages

This is a monorepo which contains many tools and packages:

Tools

Project Package Version Links
Angular CLI @angular/cli latest README snapshot
Schematics CLI @angular-devkit/schematics-cli latest snapshot

Packages

Project Package Version Links
Architect @angular-devkit/architect latest README snapshot
Architect CLI @angular-devkit/architect-cli latest snapshot
Build Angular @angular-devkit/build-angular latest README snapshot
Build NgPackagr @angular-devkit/build-ng-packagr latest README snapshot
Build Optimizer @angular-devkit/build-optimizer latest README snapshot
Build Webpack @angular-devkit/build-webpack latest README snapshot
Core @angular-devkit/core latest README snapshot
Schematics @angular-devkit/schematics latest README snapshot

Schematics

Project Package Version Links
Angular PWA Schematics @angular/pwa latest snapshot
Angular Schematics @schematics/angular latest snapshot
Schematics Schematics @schematics/schematics latest snapshot
Package Update Schematics @schematics/update latest snapshot

Misc

Project Package Version Links
Webpack Angular Plugin @ngtools/webpack latest snapshot