angular/packages/compiler/package.json
Paul Gschwendtner d2a8639b25 refactor: remove peer dependency on core from compiler (#60437)
Note that this is not a public-facing change because the compiler is not
supposed to be used directly. See `public-api-surface.md`

We are changing this because in the current state, for advanced setups
like our Bazel infrastructure in Material, this peer dependency can
result in a cycle. That is because we may decide to link the
`@angular/core` package using the compiler-cli/compiler; while
transitively the compiler has a dependency on core. That's a cycle
(surfacing in Bazel w/ `rules_js`).

Dropping this optional peer dependency is acceptable because `core`,
since recently, also has an optional peer dependency on the compiler.
This one makes more sense and is also more user-facing (people generally
never install the compiler directly).

Notably the compiler does not have any runtime dependency on `core` and
this was purely added for some safety checking. See:
8c171da29f

PR Close #60437
2025-03-18 18:15:07 +01:00

24 lines
530 B
JSON

{
"name": "@angular/compiler",
"version": "0.0.0-PLACEHOLDER",
"description": "Angular - the compiler library",
"author": "angular",
"license": "MIT",
"engines": {
"node": "^18.19.1 || ^20.11.1 || >=22.0.0"
},
"dependencies": {
"tslib": "^2.3.0"
},
"repository": {
"type": "git",
"url": "https://github.com/angular/angular.git",
"directory": "packages/compiler"
},
"ng-update": {
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
},
"sideEffects": [
"./fesm2022/compiler.mjs"
]
}