integration/injectable-def/tsconfig-lib1.json

{
  "compilerOptions": {
    "target": "es2020",
    "module": "es2020",
    "declaration": true,
    "moduleResolution": "node",
    "lib": ["es2020", "dom"],
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "outDir": "node_modules/lib1_built",
    "types": [],
    "rootDir": "."
  },
  "files": [
    "src/lib1.ts"
  ],
}
feat: change @Injectable() to support tree-shakeable tokens (#22005) This commit bundles 3 important changes, with the goal of enabling tree-shaking of services which are never injected. Ordinarily, this tree-shaking is prevented by the existence of a hard dependency on the service by the module in which it is declared. Firstly, @Injectable() is modified to accept a 'scope' parameter, which points to an @NgModule(). This reverses the dependency edge, permitting the module to not depend on the service which it "provides". Secondly, the runtime is modified to understand the new relationship created above. When a module receives a request to inject a token, and cannot find that token in its list of providers, it will then look at the token for a special ngInjectableDef field which indicates which module the token is scoped to. If that module happens to be in the injector, it will behave as if the token itself was in the injector to begin with. Thirdly, the compiler is modified to read the @Injectable() metadata and to generate the special ngInjectableDef field as part of TS compilation, using the PartialModules system. Additionally, this commit adds several unit and integration tests of various flavors to test this change. PR Close #22005 2018-02-02 10:33:48 -08:00			`{`
			`"compilerOptions": {`
test: update basic integration tests to work with new package output (#43431) Basic integration tests are those which do not require significant changes as others. The larger ones will have individual commits. For v13, the NPM package output will always be using partial compilation output. This makes the ngcc integration test fail because the actual Angular framework packages are no longer processable. We fix this, and keep the ngcc test coverage by relying on the v12.x framework packages in the integration test. The terser integration test needs to point to the new Flat ESM module file location. We now output FESM2020 instead of FESM2015. This also requires us to use the latest version of terser. The `side-effects` test currently is not maintained by us and relies on View Engine build output. In the partial compilation output the partial declarations are not marked with `@PURE` and are not removed therefore. We would need to update the side-effect test to use the linker Babel plugin instead. This is currently out-of-scope though so we disable the test for now. PR Close #43431 2021-09-20 22:12:21 +02:00			`"target": "es2020",`
			`"module": "es2020",`
feat: change @Injectable() to support tree-shakeable tokens (#22005) This commit bundles 3 important changes, with the goal of enabling tree-shaking of services which are never injected. Ordinarily, this tree-shaking is prevented by the existence of a hard dependency on the service by the module in which it is declared. Firstly, @Injectable() is modified to accept a 'scope' parameter, which points to an @NgModule(). This reverses the dependency edge, permitting the module to not depend on the service which it "provides". Secondly, the runtime is modified to understand the new relationship created above. When a module receives a request to inject a token, and cannot find that token in its list of providers, it will then look at the token for a special ngInjectableDef field which indicates which module the token is scoped to. If that module happens to be in the injector, it will behave as if the token itself was in the injector to begin with. Thirdly, the compiler is modified to read the @Injectable() metadata and to generate the special ngInjectableDef field as part of TS compilation, using the PartialModules system. Additionally, this commit adds several unit and integration tests of various flavors to test this change. PR Close #22005 2018-02-02 10:33:48 -08:00			`"declaration": true,`
			`"moduleResolution": "node",`
test: update basic integration tests to work with new package output (#43431) Basic integration tests are those which do not require significant changes as others. The larger ones will have individual commits. For v13, the NPM package output will always be using partial compilation output. This makes the ngcc integration test fail because the actual Angular framework packages are no longer processable. We fix this, and keep the ngcc test coverage by relying on the v12.x framework packages in the integration test. The terser integration test needs to point to the new Flat ESM module file location. We now output FESM2020 instead of FESM2015. This also requires us to use the latest version of terser. The `side-effects` test currently is not maintained by us and relies on View Engine build output. In the partial compilation output the partial declarations are not marked with `@PURE` and are not removed therefore. We would need to update the side-effect test to use the linker Babel plugin instead. This is currently out-of-scope though so we disable the test for now. PR Close #43431 2021-09-20 22:12:21 +02:00			`"lib": ["es2020", "dom"],`
feat: change @Injectable() to support tree-shakeable tokens (#22005) This commit bundles 3 important changes, with the goal of enabling tree-shaking of services which are never injected. Ordinarily, this tree-shaking is prevented by the existence of a hard dependency on the service by the module in which it is declared. Firstly, @Injectable() is modified to accept a 'scope' parameter, which points to an @NgModule(). This reverses the dependency edge, permitting the module to not depend on the service which it "provides". Secondly, the runtime is modified to understand the new relationship created above. When a module receives a request to inject a token, and cannot find that token in its list of providers, it will then look at the token for a special ngInjectableDef field which indicates which module the token is scoped to. If that module happens to be in the injector, it will behave as if the token itself was in the injector to begin with. Thirdly, the compiler is modified to read the @Injectable() metadata and to generate the special ngInjectableDef field as part of TS compilation, using the PartialModules system. Additionally, this commit adds several unit and integration tests of various flavors to test this change. PR Close #22005 2018-02-02 10:33:48 -08:00			`"experimentalDecorators": true,`
			`"emitDecoratorMetadata": true,`
			`"outDir": "node_modules/lib1_built",`
			`"types": [],`
			`"rootDir": "."`
			`},`
			`"files": [`
			`"src/lib1.ts"`
			`],`
test: update basic integration tests to work with new package output (#43431) Basic integration tests are those which do not require significant changes as others. The larger ones will have individual commits. For v13, the NPM package output will always be using partial compilation output. This makes the ngcc integration test fail because the actual Angular framework packages are no longer processable. We fix this, and keep the ngcc test coverage by relying on the v12.x framework packages in the integration test. The terser integration test needs to point to the new Flat ESM module file location. We now output FESM2020 instead of FESM2015. This also requires us to use the latest version of terser. The `side-effects` test currently is not maintained by us and relies on View Engine build output. In the partial compilation output the partial declarations are not marked with `@PURE` and are not removed therefore. We would need to update the side-effect test to use the linker Babel plugin instead. This is currently out-of-scope though so we disable the test for now. PR Close #43431 2021-09-20 22:12:21 +02:00			`}`