Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
angular/packages/core/package.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

46 lines
1 KiB
JSON
Raw Normal View History

repackaging: all the repackaging changes squashed
2016-04-29 00:50:03 +00:00
{
"name": "@angular/core",
chore(package.json): make the packages installable
2016-05-27 23:17:16 +00:00
"version": "0.0.0-PLACEHOLDER",
docs: update descriptions in package.jsons
2016-09-14 23:44:39 +00:00
"description": "Angular - the core framework",
repackaging: all the repackaging changes squashed
2016-04-29 00:50:03 +00:00
"author": "angular",
"license": "MIT",
feat(core): 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. BREAKING CHANGE: Angular no longer maintains support for node v10 PR Close #41544
2021-04-12 19:08:28 +00:00
"engines": {
fix(core): update min Node.js support to 20.19, 22.12, and 24.0 (#61499) This is to match the versions of the Angular CLI. See: https://github.com/angular/angular-cli/pull/30349 PR Close #61499
2025-05-20 12:25:40 +00:00
"node": "^20.19.0 || ^22.12.0 || >=24.0.0"
feat(core): 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. BREAKING CHANGE: Angular no longer maintains support for node v10 PR Close #41544
2021-04-12 19:08:28 +00:00
},
refactor(migrations): ensure CommonJS migrations can be accessed (#43657) The `@angular/core` migrations are currently published as CommonJS and also not bundled. Schematics, of which migrations are a type, are currently required to be CommonJS modules due to the Schematics Runtime not yet supporting ESM-based schematics. To ensure that the migration files are loaded as CommonJS modules, a nested `package.json` file has been introduced within the `schematics` directory of the package to set the `type` field for all containing JavaScript files as CommonJS. Since the migrations are also not currently bundled and the `devmode` output used to build the migrations will replace all relative imports with fully-qualified module specifiers, an additional `exports` entry must be added to allow the fully-qualified module specifiers to correctly resolve. If `devmode` did not change the relative imports the additional entry would not be needed. Bundling would also remedy the situation and is the long-term path, especially once the migrations are converted to ESM. Additional followup changes should investigate bundling each migration. The additional `exports` entry should be removed if either `devmode` behavior is changed or the migrations are bundled. PR Close #43657
2021-10-04 16:03:19 +00:00
"exports": {
"./schematics/*": {
"default": "./schematics/*.js"
build: make JSA contract binary accessible (#55361) This commit integrates the JSA contract binary into the NPM package and ensures its accessibility by including it in the package exports. This adjustment is essential for enabling Angular CLI to effectively access and inject the script. Additionally, sourcemaps are removed from the minified bundle to prevent their inclusion in the HTML page. PR Close #55361
2024-04-16 14:39:28 +00:00
},
"./event-dispatch-contract.min.js": {
"default": "./event-dispatch-contract.min.js"
refactor(migrations): ensure CommonJS migrations can be accessed (#43657) The `@angular/core` migrations are currently published as CommonJS and also not bundled. Schematics, of which migrations are a type, are currently required to be CommonJS modules due to the Schematics Runtime not yet supporting ESM-based schematics. To ensure that the migration files are loaded as CommonJS modules, a nested `package.json` file has been introduced within the `schematics` directory of the package to set the `type` field for all containing JavaScript files as CommonJS. Since the migrations are also not currently bundled and the `devmode` output used to build the migrations will replace all relative imports with fully-qualified module specifiers, an additional `exports` entry must be added to allow the fully-qualified module specifiers to correctly resolve. If `devmode` did not change the relative imports the additional entry would not be needed. Bundling would also remedy the situation and is the long-term path, especially once the migrations are converted to ESM. Additional followup changes should investigate bundling each migration. The additional `exports` entry should be removed if either `devmode` behavior is changed or the migrations are bundled. PR Close #43657
2021-10-04 16:03:19 +00:00
}
},
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 12:35:37 +00:00
"dependencies": {
feat(core): support TypeScript 4.4 (#43281) Adds support for TypeScript 4.4. High-level overview of the changes made in this PR: * Bumps the various packages to `typescript@4.4.2` and `tslib@2.3.0`. * The `useUnknownInCatchVariables` compiler option has been disabled so that we don't have to cast error objects explicitly everywhere. * TS now passes in a third argument to the `__spreadArray` call inside child class constructors. I had to update a couple of places in the runtime and ngcc to be able to pick up the calls correctly. * TS now generates code like `(0, foo)(arg1, arg2)` for imported function calls. I had to update a few of our tests to account for it. See https://github.com/microsoft/TypeScript/pull/44624. * Our `ngtsc` test setup calls the private `matchFiles` function from TS. I had to update our usage, because a new parameter was added. * There was one place where we were setting the readonly `hasTrailingComma` property. I updated the usage to pass in the value when constructing the object instead. * Some browser types were updated which meant that I had to resolve some trivial type errors. * The downlevel decorators tranform was running into an issue where the Closure synthetic comments were being emitted twice. I've worked around it by recreating the class declaration node instead of cloning it. PR Close #43281
2021-09-22 18:50:59 +00:00
"tslib": "^2.3.0"
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 12:35:37 +00:00
},
repackaging: all the repackaging changes squashed
2016-04-29 00:50:03 +00:00
"peerDependencies": {
fix(core): added @angular/compiler as a peer dependency (#55610) This fixes an issue with packages managers likes pmpm that will not link the @angular/compiler package to the @angular/core package if it is not listed as a peer dependency. I added it as optional peer dependency as it's only used in special cases. Fixes #38096 PR Close #55610
2024-05-01 13:31:43 +00:00
"@angular/compiler": "0.0.0-PLACEHOLDER",
refactor(compiler-cli): update peerDependencies to require rxjs ^7.4.0 (#43748) RxJS 7 versions prior to 7.4.0 export ES5 code, whereas Angular applications using RxJS 6 today use ES2015. This was fixed in RxJS 7.4.0 which exposes ES2015 entrypoints as well. This commit updates Angular's peer dependencies to require the newer RxJS. PR Close #43748
2021-10-06 21:29:30 +00:00
"rxjs": "^6.5.3 || ^7.4.0",
build: update zone.js peer dependency for core package to 0.15.0 (#57431) This commit updates zone.js peer dependency versioon for core package to 0.15.0. PR Close #57431
2024-08-16 23:37:06 +00:00
"zone.js": "~0.15.0"
adds 'repository' metadata to npm modules (#8649)
2016-05-18 06:17:15 +00:00
},
fix(core): added @angular/compiler as a peer dependency (#55610) This fixes an issue with packages managers likes pmpm that will not link the @angular/compiler package to the @angular/core package if it is not listed as a peer dependency. I added it as optional peer dependency as it's only used in special cases. Fixes #38096 PR Close #55610
2024-05-01 13:31:43 +00:00
"peerDependenciesMeta": {
"@angular/compiler": {
"optional": true
fix(core): mark `zone.js` as an optional peer dependency (#61616) `zone.js` is no longer mandatory. PR Close #61616
2025-05-22 16:24:28 +00:00
},
"zone.js": {
"optional": true
fix(core): added @angular/compiler as a peer dependency (#55610) This fixes an issue with packages managers likes pmpm that will not link the @angular/compiler package to the @angular/core package if it is not listed as a peer dependency. I added it as optional peer dependency as it's only used in special cases. Fixes #38096 PR Close #55610
2024-05-01 13:31:43 +00:00
}
},
adds 'repository' metadata to npm modules (#8649)
2016-05-18 06:17:15 +00:00
"repository": {
"type": "git",
build(packaging): add repository.directory field to package.jsons (#27544) PR Close #27544
2018-12-07 11:12:59 +00:00
"url": "https://github.com/angular/angular.git",
"directory": "packages/core"
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 23:04:35 +00:00
},
"ng-update": {
build: update zone.js to 0.9.0 (#28219) The API changes are due to enabling strict checks in TypeScript (via `strict: true`). The payload size changes in `polyfills.js` are due to more browser APIs being patched in recent versions (e.g. `fetch`, `customElement v1`). PR Close #28219
2019-01-18 00:52:34 +00:00
"migrations": "./schematics/migrations.json",
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 23:04:35 +00:00
"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-15 01:30:18 +00:00
},
build: set up ng generate schematics for core (#48790) Adds the necessary boilerplate to allow for `ng generate` schematics to be included with `@angular/core`. PR Close #48790
2023-01-20 08:34:53 +00:00
"schematics": "./schematics/collection.json",
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 19:20:11 +00:00
"sideEffects": false
feat(core): add support for Node.js version 18 (#47730) This change aligns with the supported Node.js versions of the Angular CLI. See: https://github.com/angular/angular-cli/pull/24026 BREAKING CHANGE: Angular no longer supports Node.js versions `14.[15-19].x` and `16.[10-12].x`. Current supported versions of Node.js are `14.20.x`, `16.13.x` and `18.10.x`. PR Close #47730
2022-10-11 12:39:05 +00:00
}
Reference in a new issue Copy permalink