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

37 lines
878 B
JSON
Raw Normal View History

chore: set up test and build infrastructure
2016-05-20 16:22:57 -04:00
{
chore(router): update config before publishing to npm
2016-06-08 20:00:05 -04:00
"name": "@angular/router",
build: update router package.json placeholder (#17060)
2017-05-30 16:19:54 -04:00
"version": "0.0.0-PLACEHOLDER",
docs: update descriptions in package.jsons
2016-09-14 19:44:39 -04:00
"description": "Angular - the routing library",
chore: set up test and build infrastructure
2016-05-20 16:22:57 -04:00
"keywords": [
"angular",
"router"
],
"repository": {
"type": "git",
build(packaging): add repository.directory field to package.jsons (#27544) PR Close #27544
2018-12-07 06:12:59 -05:00
"url": "git+https://github.com/angular/angular.git",
"directory": "packages/router"
chore: set up test and build infrastructure
2016-05-20 16:22:57 -04:00
},
chore(router): changes the router setup to align with other modules
2016-06-21 13:35:42 -04:00
"author": "angular",
chore: set up test and build infrastructure
2016-05-20 16:22:57 -04:00
"license": "MIT",
feat(router): update supported range of node versions (#41544) Update the supported range of node versions for Angular. Angular now supports node >=12.14.1 to <16.0.0, dropping support for Node v10. PR Close #41544
2021-04-12 15:13:09 -04:00
"engines": {
build(router): update supported range of node versions to be less restrictive (#42205) Update the supported range of node versions for to be less restrictive, no longer causing yarn or npm to fail engine's checks for future versions of node. While this change will no longer cause yarn or npm to fail these engine's check, this does not reflect a change in the officially supported versions of node for Angular. Angular continues to maintain support for Active LTS and Maintenance LTS versions of node. PR Close #42205
2021-05-20 15:34:30 -04:00
"node": "^12.14.1 || >=14.0.0"
feat(router): update supported range of node versions (#41544) Update the supported range of node versions for Angular. Angular now supports node >=12.14.1 to <16.0.0, dropping support for Node v10. PR Close #41544
2021-04-12 15:13:09 -04:00
},
chore: set up test and build infrastructure
2016-05-20 16:22:57 -04:00
"bugs": {
chore(router): remove lint and format tasks from router
2016-06-20 14:48:08 -04:00
"url": "https://github.com/angular/angular/issues"
chore: set up test and build infrastructure
2016-05-20 16:22:57 -04:00
},
fix(router): fix outdated homepage url in NPM package (#17899)
2017-07-11 15:00:56 -04:00
"homepage": "https://github.com/angular/angular/tree/master/packages/router",
build: import tslib rather than output TS helpers (#16901)
2017-05-23 16:01:39 -04:00
"dependencies": {
feat(core): support TypeScript 4.2 (#41158) Updates the repo to TypeScript 4.2 and tslib 2.1.0. PR Close #41158
2021-03-16 15:10:32 -04:00
"tslib": "^2.1.0"
build: import tslib rather than output TS helpers (#16901)
2017-05-23 16:01:39 -04:00
},
chore(router): changes the router setup to align with other modules
2016-06-21 13:35:42 -04:00
"peerDependencies": {
"@angular/core": "0.0.0-PLACEHOLDER",
"@angular/common": "0.0.0-PLACEHOLDER",
fix(router): add a banner file for the router (#12919)
2016-11-16 12:17:19 -05:00
"@angular/platform-browser": "0.0.0-PLACEHOLDER",
refactor: update to tslib 2.0 and move to direct dependencies (#37198) Tslib version is bound to the TypeScript version used to compile the library. Thus, we shouldn't list `tslib` as a `peerDependencies`. This is because, a user can install libraries which have been compiled with older versions of TypeScript and thus require multiple `tslib` versions to be installed. Reference: TOOL-1374 and TOOL-1375 Closes: #37188 PR Close #37198
2020-05-19 08:35:37 -04:00
"rxjs": "^6.5.3"
release: add ng update package group metadata to angular (#22482) "ng update" supports having multiple packages as part of a group which should be updated together, meaning that e.g. calling "ng update @angular/core" would be equivalent to updating all packages of the group (that are part of the package.json already). In order to support the grouping feature, the package.json of the version the user is updating to needs to include an "ng-update" key that points to this metadata. The entire specification for the update workflow can be found here: https://github.com/hansl/devkit/blob/2e8b12a4ef53833dc006e8711acf95cf3a6cf24e/docs/specifications/update.md PR Close #22482
2018-02-27 18:04:35 -05:00
},
"ng-update": {
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
feat: mark angular packages as side-effect free (#22785) This flag is picked up by webpack v4 and used for more agressive optimizations. Our code is already side-effect free, because that's what we needed for build-optimizer to work. PR Close #22785
2018-03-14 21:30:18 -04:00
},
build: remove publishConfig entry from package.json entries (#42104) Remove publishConfig property from the package.json entry for each of the entries in the publish configuration. Using the wombat proxy is now ensured/managed by the ng-dev release tooling. PR Close #42104
2021-05-14 15:20:11 -04:00
"sideEffects": false
chore(typings): use typings instead of tsd
2016-05-20 17:43:07 -04:00
}