Users should be able to add Bazel workspace to an existing project.
The current approach assumes that the schematics is working on the same
tree as that of ng-new, which includes the top-level directory. Instead,
the schematic should work on the tree rooted at `appRoot` to enable
Bazel files to be added to existing project.
This change uses the newly implemented ScopedTree
a0ac4b0e3d
to achieve this.
NOTE: The version of `@angular-devkit/schematics` that is installed is
used to run the `@angular/bazel` schematic. Even if a different version
is used in the schematic itself, it has no effect.
Therefore, the *latest* Angular CLI should be used to generate the
files. As of this commit, the latest version is @angular/cli@7.3.0-rc.0
PR Close #28349
42 lines
1.2 KiB
JSON
42 lines
1.2 KiB
JSON
{
|
|
"name": "@angular/bazel",
|
|
"version": "0.0.0-PLACEHOLDER",
|
|
"description": "Angular - bazel build rules",
|
|
"author": "angular",
|
|
"license": "MIT",
|
|
"bin": {
|
|
"ngc-wrapped": "./src/ngc-wrapped/index.js",
|
|
"packager": "./src/ng_package/packager.js",
|
|
"xi18n": "./src/ngc-wrapped/extract_i18n.js",
|
|
"modify_tsconfig": "./src/modify_tsconfig.js"
|
|
},
|
|
"typings": "./src/ngc-wrapped/index.d.ts",
|
|
"dependencies": {
|
|
"@angular-devkit/architect": "^0.10.6",
|
|
"@angular-devkit/core": "^7.0.4",
|
|
"@angular-devkit/schematics": "^7.3.0-rc.0",
|
|
"@bazel/typescript": "^0.22.1",
|
|
"@schematics/angular": "^7.0.4",
|
|
"@types/node": "6.0.84",
|
|
"semver": "^5.6.0",
|
|
"shelljs": "0.8.2",
|
|
"tsickle": "0.34.0"
|
|
},
|
|
"peerDependencies": {
|
|
"@angular/compiler-cli": "0.0.0-PLACEHOLDER",
|
|
"typescript": ">=3.1.1 <3.3"
|
|
},
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "https://github.com/angular/angular.git"
|
|
},
|
|
"builders": "./src/builders/builders.json",
|
|
"schematics": "./src/schematics/collection.json",
|
|
"ng-update": {
|
|
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
|
|
},
|
|
"scripts": {
|
|
"postinstall": "node ./check_version.js"
|
|
}
|
|
}
|