iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/packages/bazel/package.json

42 lines
1.2 KiB
JSON
Raw Normal View History

refactor(compiler-cli): move ngc-wrapped to packages/bazel (#18733) See design: https://goo.gl/rAeYWx PR Close #18733
2017-08-16 12:02:20 -04:00
{
"name": "@angular/bazel",
"version": "0.0.0-PLACEHOLDER",
"description": "Angular - bazel build rules",
"author": "angular",
"license": "MIT",
build: idiomatic install of @angular/bazel npm package (#26258) (#26488) PR Close #26488
2018-10-16 16:20:00 -04:00
"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",
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
"dependencies": {
build(bazel): Add Bazel builders (#27141) PR Close #27141
2018-11-16 14:36:17 -05:00
"@angular-devkit/architect": "^0.10.6",
feat(bazel): Bazel workspace schematics (#26971) This commit creates a schematics for Bazel workspace. PR Close #26971
2018-09-14 10:03:29 -04:00
"@angular-devkit/core": "^7.0.4",
fix(bazel): Bazel-workspace schematics should run in ScopedTree (#28349) 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 https://github.com/angular/angular-cli/commit/a0ac4b0e3dd60c75e1edafd6bb8cced47d10a8d3 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
2019-01-17 14:35:06 -05:00
"@angular-devkit/schematics": "^7.3.0-rc.0",
build(bazel): Bump @bazel/typescript & @bazel/karma to 0.22.1 (#28031) PR Close #28031
2019-01-09 19:22:06 -05:00
"@bazel/typescript": "^0.22.1",
feat(bazel): Bazel workspace schematics (#26971) This commit creates a schematics for Bazel workspace. PR Close #26971
2018-09-14 10:03:29 -04:00
"@schematics/angular": "^7.0.4",
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
"@types/node": "6.0.84",
fix(bazel): Read latest versions from latest-versions.ts & use semver check (#27526) When @angular/bazel is installed, a postinstall script is run to make sure that the npm version is *exactly* the same as the Angular repository install by Bazel. This check is overly stringent. Instead, it should enforce that the version satisfies the range check instead. This is consistent with the range defined in angular-cli/packages/schematics/angular/utility/latest-versions.ts. This commit also fixes the Bazel workspace to use the same Rxjs version if it's already installed. PR Close #27526
2018-12-06 18:46:36 -05:00
"semver": "^5.6.0",
build: review comments addressed (#26488) PR Close #26488
2018-10-18 12:58:38 -04:00
"shelljs": "0.8.2",
fix(bazel): tsickle dependency not working with typescript 3.1.x (#27402) `@angular/bazel` currently requires TypeScript 3.1.x as a peer dependency, but comes with `tsickle` as dependency. The current version of `tsickle` that is specified by `@angular/bazel` does not support TypeScript 3.1.x (which is a peer dependency) and therefore we need to make sure that `tsickle` works with the required TypeScript versions. This change updates `tsickle` to the latest version that comes with https://github.com/angular/tsickle/commit/b10fb6de0a86646e0f15c8551e77a0b4c5956f8b in order to work with TypeScript 3.1.x. PR Close #27402
2018-12-02 14:06:56 -05:00
"tsickle": "0.34.0"
feat(bazel): add an ng_package rule (#22221) This produces a directory following the Angular Package layout spec. Includes integration test coverage by making a minimal ng_package in integration/bazel. Unit tests verify the content of the @angular/core and @angular/common packages. This doesn't totally match our current output, but is good enough to unblock some early adopters. It re-uses logic from the rollup_bundle rule in rules_nodejs. It should also eventually have the .pack and .publish secondary targets like npm_package rule. PR Close #22221
2018-02-13 14:26:06 -05:00
},
refactor(compiler-cli): move ngc-wrapped to packages/bazel (#18733) See design: https://goo.gl/rAeYWx PR Close #18733
2017-08-16 12:02:20 -04:00
"peerDependencies": {
"@angular/compiler-cli": "0.0.0-PLACEHOLDER",
feat: add support for typescript 3.2 (#27536) https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-2.html https://blogs.msdn.microsoft.com/typescript/2018/11/29/announcing-typescript-3-2/ Any application using tsickle for closure compatibility will need to update it's tsickle dependency to 0.34 PR Close #27536
2018-12-07 02:01:08 -05:00
"typescript": ">=3.1.1 <3.3"
refactor(compiler-cli): move ngc-wrapped to packages/bazel (#18733) See design: https://goo.gl/rAeYWx PR Close #18733
2017-08-16 12:02:20 -04:00
},
"repository": {
"type": "git",
"url": "https://github.com/angular/angular.git"
feat(bazel): change ng_package rule to APF v6 (#22782) Angular Package Format v6 stops bundling files in the esm5 and esm2015 directories, now that Webpack 4 can tree-shake per-file. Adds some missing files like package.json to make packages closer to what we publish today. Refactor ng_package to be a type of npm_package and re-use the packaging action from that rule. PR Close #22782
2018-03-13 14:00:53 -04:00
},
build(bazel): Add Bazel builders (#27141) PR Close #27141
2018-11-16 14:36:17 -05:00
"builders": "./src/builders/builders.json",
feat(bazel): Bazel workspace schematics (#26971) This commit creates a schematics for Bazel workspace. PR Close #26971
2018-09-14 10:03:29 -04:00
"schematics": "./src/schematics/collection.json",
feat(bazel): change ng_package rule to APF v6 (#22782) Angular Package Format v6 stops bundling files in the esm5 and esm2015 directories, now that Webpack 4 can tree-shake per-file. Adds some missing files like package.json to make packages closer to what we publish today. Refactor ng_package to be a type of npm_package and re-use the packaging action from that rule. PR Close #22782
2018-03-13 14:00:53 -04:00
"ng-update": {
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
build: idiomatic install of @angular/bazel npm package (#26258) (#26488) PR Close #26488
2018-10-16 16:20:00 -04:00
},
"scripts": {
"postinstall": "node ./check_version.js"
refactor(compiler-cli): move ngc-wrapped to packages/bazel (#18733) See design: https://goo.gl/rAeYWx PR Close #18733
2017-08-16 12:02:20 -04:00
}
build(bazel): Bump @bazel/typescript & @bazel/karma to 0.22.1 (#28031) PR Close #28031
2019-01-09 19:22:06 -05:00
}