b7138c1ec5
The dev-infra package currently uses rollup for packaging. This has been done initially as a way to workaround manifest paths being used in the AMD JavaScript output. The actual solution to this problem is setting module names that match the `package.json` name. This ensures that the package can be consumed correctly in Bazel, and through NPM. This allows us to get rid of the rollup bundling, and we don't need to hard-code which dependencies should be external or included. Additionally, tools that are part of `dev-infra` can now specify their external dependencies simply in the `package.json`. To reduce version duplication, and out-of-sync versions, a new genrule has been created that syncs the versions with the top-level project `package.json`. PR Close #35647
22 lines
571 B
JSON
22 lines
571 B
JSON
{
|
|
"name": "@angular/dev-infra-private",
|
|
"version": "0.0.0",
|
|
"description": "INTERNAL USE ONLY - Angular internal DevInfra tooling/scripts - INTERNAL USE ONLY",
|
|
"license": "MIT",
|
|
"private": true,
|
|
"bin": {
|
|
"ng-dev": "./cli.js",
|
|
"ts-circular-deps": "./ts-circular-dependencies/index.js"
|
|
},
|
|
"peerDependencies": {
|
|
"chalk": "<from-root>",
|
|
"glob": "<from-root>",
|
|
"minimatch": "<from-root>",
|
|
"shelljs": "<from-root>",
|
|
"typescript": "<from-root>",
|
|
"yaml": "<from-root>",
|
|
"yargs": "<from-root>",
|
|
"tslib": "<from-root>"
|
|
}
|
|
}
|