问题描述
我正在遵循使用 JitCompilerFactory
加载的解决方案here运行时编译器和自定义装饰器以保留组件和模块元数据.但是使用 angular-cli --build-optimizer
标志我得到:
I am following the solution here of using the JitCompilerFactory
to load the runtime compiler and custom decorators to preserve the component and module metadata. But with the angular-cli --build-optimizer
flag I get:
ERROR 错误:无法解析解析器"(?) 的所有参数.确保所有参数都用 Inject 修饰或具有有效的类型注释,并且Parser"用 Injectable 修饰.
这里是我的最小复制,运行 ng serve --aot --构建优化器
.作为控制 ng serve --aot
工作.
Here is my minimal reproduction, run ng serve --aot --build-optimizer
. As a control ng serve --aot
works.
推荐答案
如果你使用选项 --build-optimizer
然后 @angular-devkit/build-optimizer/webpack-loader
loader 被添加到 webpack loaders 列表中.
If you use option --build-optimizer
then @angular-devkit/build-optimizer/webpack-loader
loader is added to webpack loaders list.
@angular-devkit/build-optimizer/webpack-loader
从不属于 platformWhitelist
(source):
const platformWhitelist = [
'PlatformRef_',
'TestabilityRegistry',
'Console',
'BrowserPlatformLocation',
];
我认为这是正确的行为.
I think that's correct behavior.
要解决这个问题,您可以在 JitCompilerFactory
:
To work around it you could initialize ctorParameters
manually before JitCompilerFactory
is created:
import {
Compiler, ɵConsole as Console,
Optional, Inject, Injector,
PACKAGE_ROOT_URL
} from '@angular/core';
import {
JitCompilerFactory,
TemplateParser, CompilerConfig, CompileReflector,
ElementSchemaRegistry, I18NHtmlParser, TEMPLATE_TRANSFORMS, DirectiveNormalizer,
ResourceLoader, UrlResolver, HtmlParser, CompileMetadataResolver, NgModuleResolver,
DirectiveResolver, SummaryResolver, PipeResolver, StaticSymbolCache,
ERROR_COLLECTOR_TOKEN,
StyleCompiler, ViewCompiler, NgModuleCompiler, JitCompiler
} from '@angular/compiler';
import * as compiler from '@angular/compiler';
export function compilerFactory() {
restoreDecorators();
return new JitCompilerFactory([{ useDebug: false, useJit: true }]).createCompiler();
}
function restoreDecorators() {
(compiler.Parser as any).parameters = [compiler.Lexer];
(TemplateParser as any).parameters = [
CompilerConfig, CompileReflector, compiler.Parser, ElementSchemaRegistry,
I18NHtmlParser, Console, [new Optional(), new Inject(TEMPLATE_TRANSFORMS)]
];
(DirectiveNormalizer as any).parameters = [
ResourceLoader, UrlResolver,
HtmlParser, CompilerConfig
];
(CompileMetadataResolver as any).parameters = [
CompilerConfig, NgModuleResolver, DirectiveResolver, PipeResolver, SummaryResolver,
ElementSchemaRegistry,
DirectiveNormalizer, Console,
[new Optional(), StaticSymbolCache],
CompileReflector,
[new Optional(), new Inject(ERROR_COLLECTOR_TOKEN)]
];
(StyleCompiler as any).parameters = [UrlResolver];
(ViewCompiler as any).parameters = [CompileReflector];
(NgModuleCompiler as any).parameters = [CompileReflector];
(NgModuleResolver as any).parameters = [CompileReflector];
(DirectiveResolver as any).parameters = [CompileReflector];
(PipeResolver as any).parameters = [CompileReflector];
(JitCompiler as any).parameters = [
Injector,
CompileMetadataResolver,
TemplateParser,
StyleCompiler,
ViewCompiler,
NgModuleCompiler,
SummaryResolver,
CompilerConfig,
Console
];
(UrlResolver as any).parameters = [[new Inject(PACKAGE_ROOT_URL)]];
}
而且这似乎有风险,因为编译器会受到内部变化的影响.它适用于 @angular/compiler@4.4.5
但可能不适用于其他版本.
And it seems to be risky as compiler is subject to internal changes. It works for @angular/compiler@4.4.5
but may not work for other releases.
这篇关于带有构建优化器的 AOT 和 JIT的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!