Chuck Jazdzewski
39a2c39cef
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.
27 lines
773 B
TypeScript
27 lines
773 B
TypeScript
import * as ts from 'typescript';
|
|
|
|
interface Options extends ts.CompilerOptions {
|
|
// Absolute path to a directory where generated file structure is written
|
|
genDir: string;
|
|
|
|
// Path to the directory containing the tsconfig.json file.
|
|
basePath: string;
|
|
|
|
// Don't produce .metadata.json files (they don't work for bundled emit with --out)
|
|
skipMetadataEmit: boolean;
|
|
|
|
// Produce an error if the metadata written for a class would produce an error if used.
|
|
strictMetadataEmit: boolean;
|
|
|
|
// Don't produce .ngfactory.ts or .css.shim.ts files
|
|
skipTemplateCodegen: boolean;
|
|
|
|
// Print extra information while running the compiler
|
|
trace: boolean;
|
|
|
|
// Whether to embed debug information in the compiled templates
|
|
debug?: boolean;
|
|
}
|
|
|
|
export default Options;
|