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.
28 lines
610 B
JSON
28 lines
610 B
JSON
{
|
|
"compilerOptions": {
|
|
"baseUrl": ".",
|
|
"declaration": true,
|
|
"stripInternal": true,
|
|
"experimentalDecorators": true,
|
|
"module": "es2015",
|
|
"moduleResolution": "node",
|
|
"outDir": "../../../dist/packages-dist/core/esm",
|
|
"paths": {
|
|
"rxjs/*": ["../../../node_modules/rxjs/*"]
|
|
},
|
|
"rootDir": ".",
|
|
"sourceMap": true,
|
|
"inlineSources": true,
|
|
"target": "es2015"
|
|
},
|
|
"files": [
|
|
"index.ts",
|
|
"testing.ts",
|
|
"../../../node_modules/zone.js/dist/zone.js.d.ts",
|
|
"../../system.d.ts"
|
|
],
|
|
"angularCompilerOptions": {
|
|
"strictMetadataEmit": true
|
|
}
|
|
}
|