iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/modules/@angular/upgrade/tsconfig-build.json

34 lines
1009 B
JSON
Raw Normal View History

repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
{
"compilerOptions": {
"baseUrl": ".",
"declaration": true,
build: turn on tsc's stripInternal when producint public d.ts file I also made some changes to fix imports and remove some stuff that caused breakage once stripInternals was turned on.
2016-05-19 18:29:50 -04:00
"stripInternal": true,
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
"experimentalDecorators": true,
"module": "es2015",
"moduleResolution": "node",
fix(packages): use ES modules for primary build (#11120)
2016-08-30 21:07:40 -04:00
"outDir": "../../../dist/packages-dist/upgrade",
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
"paths": {
"@angular/core": ["../../../dist/packages-dist/core"],
"@angular/common": ["../../../dist/packages-dist/common"],
"@angular/compiler": ["../../../dist/packages-dist/compiler"],
fix: split dynamic bits in platform-browser into platform-browser-dynamic Previously these symbols were exposed via platform-browser-dynamic, then we merged then into platform-browser thinking that tools would know how to shake off the compiler and other dynamic bits not used with the offline compilation flow. This turned out to be wrong as both webpack and rollup don't have good enough tree-shaking capabilities to do this today. We think that in the future we'll be able to merge these two entry points into one, but we need to give tooling some time before we can do it. In the meantime the reintroduction of the -dynamic package point allows us to separate the compiler dependencies from the rest of the framework. This change undoes the previous breaking change that removed the platform-browser-dynamic package.
2016-06-10 13:21:53 -04:00
"@angular/platform-browser": ["../../../dist/packages-dist/platform-browser"],
"@angular/platform-browser-dynamic": ["../../../dist/packages-dist/platform-browser-dynamic"]
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
},
"rootDir": ".",
"sourceMap": true,
build: fix source map paths for npm packages the bundles have source mpas disabled for now because when we downlevel the esm bundle to es5 tsc doesn't consider the original source map so we end up with a source map pointing to the esm bundle instead which is not useful.
2016-05-02 22:45:52 -04:00
"inlineSources": true,
fix(packages): use ES modules for primary build (#11120)
2016-08-30 21:07:40 -04:00
"target": "es5",
"skipLibCheck": true,
"lib": [ "es2015", "dom" ]
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
},
"files": [
"index.ts",
refactor(upgrade): re-export the new static upgrade APIs on new entry Add upgrade-static.umd.js bundles This allows depending on it without getting a transitive dependency on compiler. BREAKING CHANGE: Four newly added APIs in 2.2.0-beta: downgradeComponent, downgradeInjectable, UpgradeComponent, and UpgradeModule are no longer exported by @angular/upgrade. Import these from @angular/upgrade/static instead.
2016-10-20 22:35:35 -04:00
"static.ts",
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
"../../../node_modules/zone.js/dist/zone.js.d.ts"
feat(compiler): Added "strictMetadataEmit" option to ngc (#10951) ngc can now validate metadata before emitting to verify it doesn't contain an error symbol that will result in a runtime error if it is used by the StaticReflector. To enable this add the section, "angularCompilerOptions": { "strictMetadataEmit": true } to the top level of the tsconfig.json file passed to ngc. Enabled metadata validation for packages that are intended to be used statically.
2016-08-22 20:37:48 -04:00
],
"angularCompilerOptions": {
feature(tsc-wrapped): add option for closure compiler JSDoc annotations
2016-11-16 19:42:24 -05:00
"annotateForClosureCompiler": true,
feat(compiler): Added "strictMetadataEmit" option to ngc (#10951) ngc can now validate metadata before emitting to verify it doesn't contain an error symbol that will result in a runtime error if it is used by the StaticReflector. To enable this add the section, "angularCompilerOptions": { "strictMetadataEmit": true } to the top level of the tsconfig.json file passed to ngc. Enabled metadata validation for packages that are intended to be used statically.
2016-08-22 20:37:48 -04:00
"strictMetadataEmit": true
}
repackaging: all the repackaging changes squashed
2016-04-28 20:50:03 -04:00
}