mirror of https://github.com/angular/angular-cli.git synced 2025-05-15 01:54:04 +08:00

History

Charles Lyding 7f93735e98 build: use bazel to perform release builds

When performing a release via the dev-infra `ng-dev` tooling, the release
builds for the packages that will be published are now performed using bazel.
Prior to this, the release builds were performed using a custom build script
that programmatically invoked TypeScript APIs. The Bazel build and discovery
process for the releasable packages is performed by a script that is based on
the scripts from components and framework repositories. Several small modifications
were performed to match the behavior and structure of the cli repository:
* Use of `packages` as the source root in the bazel query
* Use of `pkg_npm` rule in the bazel query
* Partial transition to native Node.js `fs` APIs instead of `shelljs`
* Directory creation per package when copying output (supports multiple package scopes)
* Copying of archives (tgz) for each package

The snapshot and local build capabilities are not modified as part of this change
but will be merged in a followup as part of a larger transition to use bazel
throughout the package build process.

2023-01-05 03:21:58 +00:00

src

fix(@angular/create): use appropriate package manager to install dependencies

2022-07-22 14:00:57 -04:00

BUILD.bazel

build: use bazel to perform release builds

2023-01-05 03:21:58 +00:00

package.json

feat(@angular/create): add support for yarn create and npm init

2022-07-12 10:19:23 -07:00

README.md

Revert "docs: remove @latest reference from npm init command"

2022-11-29 14:37:16 +00:00

README.md

`@angular/create`

Create an Angular CLI workspace

Scaffold an Angular CLI workspace without needing to install the Angular CLI globally. All of the ng new options and features are supported.

Usage

npm

npm init @angular@latest [project-name] -- [...options]

yarn

yarn create @angular [project-name] [...options]

pnpm

pnpm create @angular [project-name] [...options]