mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
1f1039475c
Historically we've had to be VERY cautious about the way we import things between entry-points. That is because the `ng_package` rule bundling is subject to silently introducing code duplication, breaking singletons etc. We've had this surface a couple of times already, and dev-infra tried to help detect such cases by adding safety analysis into `ng_package`. Long-term we want to get to an approach where it's easy to simply share code between chunks. Precisely, with the upcoming `rules_js` migration, this will be necessary as we will have different import "guidelines" that would currently, before this commit, result in code duplication, or trigger our "safety check/lint". This commit prepares `ng_package` to support relative imports between entry-points, so that we only need the safety check for cross-package imports/exports. The result is that `ng_package`/APF is now smartly able to generate shared chunks for things that are needed between multiple entry-points. Yay! Note that those shared chunks still remain private, and are guarded by our `package.json` "exports"; so no new public API surface is exposed. PR Close #60241
32 lines
685 B
JSON
32 lines
685 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"
|
|
},
|
|
"peerDependencies": {
|
|
"@angular/core": "0.0.0-PLACEHOLDER"
|
|
},
|
|
"peerDependenciesMeta": {
|
|
"@angular/core": {
|
|
"optional": true
|
|
}
|
|
},
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "https://github.com/angular/angular.git",
|
|
"directory": "packages/compiler"
|
|
},
|
|
"ng-update": {
|
|
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
|
|
},
|
|
"sideEffects": [
|
|
"./fesm2022/compiler.mjs"
|
|
]
|
|
}
|