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
angular/packages/platform-browser-dynamic/package.json

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

32 lines
865 B
JSON
Raw Normal View History

feat(platform-browser-dynamic): re-add a deprecated platform-browser-dynamic
2016-05-24 23:13:17 +00:00
{
"name": "@angular/platform-browser-dynamic",
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 - library for using Angular in a web browser with JIT compilation",
feat(platform-browser-dynamic): re-add a deprecated platform-browser-dynamic
2016-05-24 23:13:17 +00:00
"author": "angular",
"license": "MIT",
feat(platform-browser-dynamic): 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. PR Close #41544
2021-04-12 19:12:55 +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(platform-browser-dynamic): 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. PR Close #41544
2021-04-12 19:12:55 +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
},
feat(platform-browser-dynamic): re-add a deprecated platform-browser-dynamic
2016-05-24 23:13:17 +00:00
"peerDependencies": {
chore(package.json): make the packages installable
2016-05-27 23:17:16 +00:00
"@angular/core": "0.0.0-PLACEHOLDER",
"@angular/common": "0.0.0-PLACEHOLDER",
"@angular/compiler": "0.0.0-PLACEHOLDER",
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
"@angular/platform-browser": "0.0.0-PLACEHOLDER"
chore(npm): add repository metadata
2016-06-20 15:49:43 +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/platform-browser-dynamic"
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": {
"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
},
fix(platform-browser-dynamic): ensure compiler is loaded before `@angular/common` (#60458) With the recent changes to the APF bundling rules, we turned on tree-shaking in rollup to support proper code splitting for FESM bundles. This resulted in Rollup re-ordering imports in the FESM bundles of `@angular/platform-browser-dynamic`— highlighting that over the past years, this package "accidentally" resulted in the side-effects of the compiler registering itself globally. This continues to be the case, and our changes generally didn't cause any issues in CLI applications because the CLI explicitly wires up the compiler (as expected) before `-dynamic` is even loaded. For custom setup, like Analog, this order change surfaced a breakage because e.g. `@angular/common` with its JIT decorators of e.g. directives/services are triggered before the compiler is actually loaded/made available. This commit fixes this. The explicit imports in practice are a noop because our FESM bundling doesn't recognize compiler as side-effects true; but marking the whole -dynamic package as having side-effects; prevents rollup from swapping the import order. Long-term, we should look into improving this by teaching `ng_package` that e.g. the compiler has side-effects; so that the `import @angular/compiler` statement is not dropped when constructing FESM bundles. PR Close #60458
2025-03-19 12:59:29 +00:00
"sideEffects": [
"./fesm2022/platform-browser-dynamic.mjs",
"./fesm2022/testing.mjs"
]
chore(package.json): make the packages installable
2016-05-27 23:17:16 +00:00
}
Reference in a new issue Copy permalink