🐞 Bug report regarding docs
Is this a regression?
No
Description
Lack of documentation for @ngtools/webpack interface makes creating environment that could be moved to angular-cli somewhere in time extremely difficult. This is very important for hybrid apps because in 99% they already have established building process and it's impossible to switch to angular-cli.
🔬 Minimal Reproduction
Open README.md of @ngtools/webpack and compare with AngularCompilerPluginOptions interface.
🔥 Exception or Error
Undocumented options:
hostReplacementPaths?: {
[path: string]: string;
} | ((path: string) => string);
forkTypeChecker?: boolean;
i18nInFile?: string;
i18nInFormat?: string;
i18nOutFile?: string;
i18nOutFormat?: string;
locale?: string;
missingTranslation?: string;
platform?: PLATFORM;
nameLazyFiles?: boolean;
logger?: logging.Logger;
discoverLazyRoutes?: boolean;
additionalLazyModules?: {
[module: string]: string;
};
additionalLazyModuleResources?: string[];
host?: virtualFs.Host;
platformTransformers?: ts.TransformerFactory[];
🌍 Your Environment
🐞 Bug report regarding docs
Is this a regression?
No
Description
Lack of documentation for
@ngtools/webpackinterface makes creating environment that could be moved toangular-clisomewhere in time extremely difficult. This is very important for hybrid apps because in 99% they already have established building process and it's impossible to switch toangular-cli.🔬 Minimal Reproduction
Open README.md of
@ngtools/webpackand compare withAngularCompilerPluginOptionsinterface.🔥 Exception or Error
Undocumented options:
🌍 Your Environment