integration/cli-hello-world/tsconfig.json

{
  "compileOnSave": false,
  "compilerOptions": {
    "outDir": "./dist/out-tsc",
    "sourceMap": true,
    "declaration": false,
    "moduleResolution": "node",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "importHelpers": true,
    "target": "es5",
    "typeRoots": [
      "node_modules/@types"
    ],
    "lib": [
      "es2017",
      "dom"
    ]
  }
}
ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555 2018-01-16 07:09:59 -08:00			`{`
			`"compileOnSave": false,`
			`"compilerOptions": {`
			`"outDir": "./dist/out-tsc",`
			`"sourceMap": true,`
			`"declaration": false,`
			`"moduleResolution": "node",`
			`"emitDecoratorMetadata": true,`
			`"experimentalDecorators": true,`
build: upgrade `cli-hello-world[-ivy]` integration projects to @angular/cli@7.2.1 (#27697) PR Close #27697 2019-01-09 20:53:18 +02:00			`"importHelpers": true,`
ci: Add back the CLI integration test with pinning (#21555) The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555 2018-01-16 07:09:59 -08:00			`"target": "es5",`
			`"typeRoots": [`
			`"node_modules/@types"`
			`],`
			`"lib": [`
			`"es2017",`
			`"dom"`
			`]`
			`}`
			`}`