angular/packages/compiler/package.json

{
  "name": "@angular/compiler",
  "version": "0.0.0-PLACEHOLDER",
  "description": "Angular - the compiler library",
  "author": "angular",
  "license": "MIT",
  "engines": {
    "node": "^20.19.0 || ^22.12.0 || >=24.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"
  ]
}
repackaging: all the repackaging changes squashed 2016-04-29 00:50:03 +00:00			`{`
			`"name": "@angular/compiler",`
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 compiler library",`
repackaging: all the repackaging changes squashed 2016-04-29 00:50:03 +00:00			`"author": "angular",`
			`"license": "MIT",`
feat(compiler): 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:32 +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(compiler): 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:32 +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"`
build: import tslib rather than output TS helpers (#16901) 2017-05-23 20:01:39 +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/compiler"`
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			`},`
feat(bazel): support shared chunks in `ng_package` (#60241) 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 2025-03-06 10:14:52 +00:00			`"sideEffects": [`
			`"./fesm2022/compiler.mjs"`
			`]`
build: set up all packages to publish via wombot proxy (#33747) PR Close #33747 2019-11-11 22:18:13 +00:00			`}`