honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/language-service/package.json

21 lines
483 B
JSON
Raw Normal View History

feat(language-service): add services to support editors (#12987)
2016-11-22 12:10:23 -05:00
{
"name": "@angular/language-service",
"version": "0.0.0-PLACEHOLDER",
docs: branding fixes (#14132) Angular 1.x -> AngularJS Angular 1 -> AngularJS Angular1 -> AngularJS Angular 2+ -> Angular Angular 2.0 -> Angular Angular2 -> Angular I have deliberately not touched any of the symbol names as that would cause big merge collisions with Tobias's work. All the renames are in .md, .json, and inline comments and jsdocs. PR Close #14132
2017-01-27 01:30:42 -05:00
"description": "Angular - language services",
fix(language-service): use single entry point for Ivy and View Engine (#40967) Currently there are two entry points for the `@angular/language-service` package: - `@angular/language-service` This default entry point is for View Engine LS. Through the redirection of `main` field in `package.json`, it resolves to `./bundles/language-service.js`. - `@angular/language-service/bundles/ivy.js` This secondary entry point is for Ivy LS. TypeScript recently changed the behavior of tsserver to allow only package names as plugin names [1] for security reasons. This means the secondary entry point for Ivy LS can no longer be used. We implemented a quick hack in the module resolver (in the extension repo) to fix this, but the long term fix should be in `@angular/language-service`. Here, the `main` field in `package.json` is changed to `index.js`, and in the index file we conditionally load View Engine or Ivy based on the input config. This eliminates the need for multiple entry points. As part of this PR, I also removed all source code for View Engine and Ivy included in the NPM package. Consumers of this package should run the bundled output and nothing else. This would help us prevent an accidental import that results in execution of unbundled code. [1]: https://github.com/microsoft/TypeScript/pull/42713 PR Close #40967
2021-02-23 13:51:23 -05:00
"main": "./index.js",
fix(language-service): Use index.d.ts for typings (#33043) The current `typings` value in `package.json` causes the import of `@angular/language-service` in TypeScript to be generated as ``` const language_service_1 = require("@angular/language-service/language-service"); ``` in CJS output. This breaks the import shim that overwrites the behavior of `require` at runtime. Changing the typings to `index.d.ts` fixes the issue. PR Close #33043
2019-10-08 19:02:34 -04:00
"typings": "./index.d.ts",
feat(language-service): add services to support editors (#12987)
2016-11-22 12:10:23 -05:00
"author": "angular",
"license": "MIT",
feat(language-service): 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 15:12:46 -04:00
"engines": {
build(language-service): update supported range of node versions to be less restrictive (#42205) Update the supported range of node versions for to be less restrictive, no longer causing yarn or npm to fail engine's checks for future versions of node. While this change will no longer cause yarn or npm to fail these engine's check, this does not reflect a change in the officially supported versions of node for Angular. Angular continues to maintain support for Active LTS and Maintenance LTS versions of node. PR Close #42205
2021-05-20 15:34:06 -04:00
"node": "^12.14.1 || >=14.0.0"
feat(language-service): 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 15:12:46 -04:00
},
feat(language-service): add services to support editors (#12987)
2016-11-22 12:10:23 -05:00
"repository": {
"type": "git",
build(packaging): add repository.directory field to package.jsons (#27544) PR Close #27544
2018-12-07 06:12:59 -05:00
"url": "https://github.com/angular/angular.git",
"directory": "packages/language-service"
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 18:04:35 -05:00
},
"ng-update": {
"packageGroup": "NG_UPDATE_PACKAGE_GROUP"
build: don't mark language-service package as sideEffect free (#22808) we are not sure if this is the case and we don't need this package to be optimized at the moment. PR Close #22808
2018-03-17 23:29:18 -04:00
}
feat(language-service): add services to support editors (#12987)
2016-11-22 12:10:23 -05:00
}