angular/packages/common/package.json
Paul Gschwendtner c7d37f74cf build: expose locales as package export for ES module resolution (#43431)
As part of v13, all APF packages use the `exports` field which defines
the public entry-points/mappings for a package. so-called package exports.

The `ng_package` rule creates all the necessary mappings/sub-path exports
for the entry-points of `@angular/common`. Though, since the locale files are
generated separately and are not an actual entry-point, we need to expose these
files publicly so that they can be imported/resolved by consumers.

PR Close #43431
2021-10-01 18:28:44 +00:00

38 lines
835 B
JSON

{
"name": "@angular/common",
"version": "0.0.0-PLACEHOLDER",
"description": "Angular - commonly needed directives and services",
"author": "angular",
"license": "MIT",
"engines": {
"node": "^12.14.1 || >=14.0.0"
},
"locales": "locales",
"dependencies": {
"tslib": "^2.3.0"
},
"exports": {
"./locales/global/*": {
"default": "./locales/global/*.js"
},
"./locales/*": {
"default": "./locales/*.mjs"
}
},
"peerDependencies": {
"@angular/core": "0.0.0-PLACEHOLDER",
"rxjs": "^6.5.3 || ^7.0.0"
},
"repository": {
"type": "git",
"url": "https://github.com/angular/angular.git",
"directory": "packages/common"
},
"ng-update": {
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
},
"sideEffects": [
"**/global/*.js",
"**/closure-locale.*"
]
}