Closed abansal77 closed 7 years ago
Meligy
commented
7 years ago This is an Angular compiler problem really not CLI problem.
convert any lambda () => something or function function something() {} to use export like:
export function getFlexLayoutModule() {
return FlexLayoutModule;
}
krishollenbeck
commented
7 years ago @Meligy There seems to be a lot of confusion in regards to the AOT compiler, myself included. I am also running into some of these errors. Is there a guide anywhere on how to use the AOT compiler with angular cli? I see in the Angular guide https://angular.io/docs/ts/latest/cookbook/aot-compiler.html they recommend creating a separate tsconfig, tsconfig-aot.json. If so shouldn't this be a part of @angular/cli when a new project is created?
I have also read in the change log a while back that AOT is default when using --prod flag (which is fine). But I don't think most people will realize this right away, I know I didn't. With that said, is there a way to build --prod with the JIT compiler? This also doesn't appear to be documented anywhere. Or I am just not looking in the right places. Any enlightenment/guidance on this subject would be much appreciated. Thanks,
krishollenbeck
commented
7 years ago Other relevant AOT compiler issues with similar errors:
deebloo
commented
7 years ago you can turn AOT off by saying ng build --prod --aot=false.
I however would not recommend this as the performance gains of AOT are to substantial to ignore.
The goal of AOT in the CLI is to abstract it away so that you don't have to think about it. If you want a better understanding of what the AOT compiler is/does that article you posted should do a good job walking you through the steps. There is no tsconfig.aot.json because the cli is handling all of this for you in memory, behind the scenes.
The docs for the cli are getting a lot of focus so things should improve in that regard.
krishollenbeck
commented
7 years ago @deebloo, Thanks for the response. That at least clears up my confusion about tsconfig-aot.json. I will be looking forward to those updated docs.
filipesilva
commented
7 years ago Heya, errors like Error encountered resolving symbol values statically mean that there has been some problem in statically analyzing your app.
The CLI always runs statical analysis on code to ensure it will run when compiled with AOT. This may cause a lot of static analysis errors to surface when importing your project into the CLI, or upgrading for older versions where we didn't run this kind of analysis.
A good resource on how to to debug these errors is https://github.com/rangle/angular-2-aot-sandbox#aot-dos-and-donts.
Also, the examples shown in https://angular.io/docs/ts/latest/cookbook/aot-compiler.html are not using the CLI so they are very different.
darincardin
commented
7 years ago This is like the 6th different error i have gotten while trying to configure AOT. The angular team should not put out code until it has been properly tested. My code works absolutely fine with JIT. As soon as AOT comes into the picture, i get a tidal wave of errors.
Karasuni
commented
7 years ago I've been getting stuck on this issue with the error
Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 9:15 in the original .ts file)
I don't understand what's going on. Originally my file included
export const testIndexedDBCache = new InjectionToken('testIndexedDBCache');
export let testIndexedDBCacheProvider : Provider = {
provide: testIndexedDBCache,
useFactory: () => new IndexedDBCache('test')
// ^--- position of error
};But even when I change the arrow function it still gets stuck on the same position!
export const testIndexedDBCache = new InjectionToken('testIndexedDBCache');
export let testIndexedDBCacheProvider : Provider = {
provide: testIndexedDBCache,
useFactory: function() { return new IndexedDBCache('test'); }
// ^--- position of error
};Karasuni, Angular 2 AOT is broken right now. I wasted over a week trying to update my project to work with AOT. Now I am extremely far behind, and AOT still doesn't work. My advice is to just use the Uglify plugin.
Yugloocamai
commented
7 years ago I have a project that has been ejected to Webpack that seems to build AoT ok, but when I use NGC manually I run into this error. What's the difference?
craftpip
commented
7 years ago I get this error, when i first run build watch, but later when i change a file, it builds fine, :/ strange
ERROR in Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 36:31 in the original .ts file), resolving symbol routes in E:/www/htdoc s/website/admin-src/src/app/app.routing.ts, resolving symbol AppRoutingModule in E:/www/htdocs/website/admin-src/src/app/app.routing.ts, resolving symbol AppRoutingModule in E:/www/htdocs/website/admin-src/src/app/app.routing.ts, resolving s ymbol AppRoutingModule in E:/www/htdocs/website/admin-src/src/app/app.routing.ts
lifenautjoe
commented
7 years ago Is AOT even worth all the pain it causes? Why does angular need this while other libraries are doing just fine without it? Looks a lot like a fix to a problem that shouldn't exist.
dbettini
commented
7 years ago @lifenautjoe probably because Angular is a few times larger than other libraries that do the same job, like vue.js. To be more precise, vue.js supports AOT through its loaders out of the box, but people usually don't even know that (maybe because vue.js is much smaller even without AOT so they don't feel it makes much difference, or because Angular causes so much pain while trying to set it up, so you NEED to talk about it).
irtazabbas
commented
7 years ago Without going into too much details, I worked around this by doing what the error's details suggested. Code that was erring out is:
import * as Modules from './modules';
...
imports: [
BrowserModule,
RouterModule,
].concat(Object.keys(Modules).map(key => Modules[key]))Fixed by creating a function and exporting it that creates an array out of the object Modules, like so:
export function joinImports() {
return Modules: Object.keys(Modules).map(key => Modules[key]);
}
...
imports: [
BrowserModule,
RouterModule
].concat(joinImports()),
skoropadas
commented
7 years ago @irtazabbas i tried your solution, compiling is ok, but modules are not imported
irtazabbas
commented
7 years ago With the option -aot, I had to remove the dynamic references, meaning I had to explicitly import or declare components and modules, so that it can be analyzed statically. It was a bummer because I had to and will have to write more code, but you also do get the benefits of aot compilation mode. @skoropadas
vytautas-pranskunas-
commented
7 years ago Bug Report
@NgModule({
imports: [CommonModule]
})
export class StoreModule {
static provideStore(): ModuleWithProviders {
return {
ngModule: StoreModule,
providers: [ added some providers]
};
}
}throwing an error:
"Calling function 'SotreModule', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule"I compared it with RouterModule in .ts and .js all the same. Tried to many of work arounds and nothing. In dev mode all works fine, when this code is added stright to project it works fine too, but when exported as a separate package - BAM - nothing!
Anybody?
For example RouterModule:
@NgModule({declarations: ROUTER_DIRECTIVES, exports: ROUTER_DIRECTIVES})
export class RouterModule {
constructor(@Optional() @Inject(ROUTER_FORROOT_GUARD) guard: any, @Optional() router: Router) {}
static forChild(routes: Routes): ModuleWithProviders {
return {ngModule: RouterModule, providers: [provideRoutes(routes)]};
}
}If this thing will not be resolved I will not have any other way just to drop Angular support and stay only in react since this issue with ngc aot is very old.
More than that - when compiling AOT with webpack all works fine, just after upgrading to Angular 5.0.0 ngc-weback plugin is not working any more.
here is complete code of ng-state.module.ts:
import { Inject, Injector, ModuleWithProviders, NgModule, InjectionToken } from '@angular/core';
import { CommonModule } from '@angular/common';
import { Dispatcher } from './services/dispatcher';
import { Router } from '@angular/router';
import { RouterState } from './state/router-state';
import { ServiceLocator } from './helpers/service-locator';
import { State } from './state/state';
import { StateHistory } from './state/history';
import { StateHistoryComponent } from './state/state-history';
import { Store } from './store/store';
export const INITIAL_STATE = new InjectionToken('INITIAL_STATE');
export const COLLECT_HISTORY = new InjectionToken('COLLECT_HISTORY');
export const STORE_HISTORY_ITEMS = new InjectionToken('STORE_HISTORY_ITEMS');
export const IS_PROD = new InjectionToken('IS_PROD');
export function stateFactory(initialState) {
return new State(initialState);
}
export function storeFactory(state: State<any>) {
return new Store(state);
}
export function historyFactory(store: Store<any>) {
return new StateHistory(store);
}
export function routerStateFactory(store: Store<any>, router: Router) {
return new RouterState(store, router);
}
@NgModule({
imports: [CommonModule],
declarations: [StateHistoryComponent],
exports: [StateHistoryComponent]
})
export class StoreModule {
static provideStore(initialState: any, isProd?: boolean, collectHistory?: boolean, storeHistoryItems?: number): ModuleWithProviders {
return {
ngModule: StoreModule,
providers: [
{ provide: STORE_HISTORY_ITEMS, useValue: storeHistoryItems },
{ provide: COLLECT_HISTORY, useValue: collectHistory },
{ provide: INITIAL_STATE, useValue: initialState },
{ provide: IS_PROD, useValue: isProd },
{ provide: State, useFactory: stateFactory, deps: [INITIAL_STATE] },
{ provide: Store, useFactory: storeFactory, deps: [State] },
{ provide: StateHistory, useFactory: historyFactory, deps: [Store, INITIAL_STATE] },
{ provide: RouterState, useFactory: routerStateFactory, deps: [Store, Router] },
Dispatcher
]
};
}
constructor(
injector: Injector,
stateHistory: StateHistory,
routerState: RouterState,
@Inject(INITIAL_STATE) initialState: any,
@Inject(STORE_HISTORY_ITEMS) storeHistoryItems: any,
@Inject(COLLECT_HISTORY) collectHistory: any,
@Inject(IS_PROD) isProd: any
) {
if (storeHistoryItems !== undefined) {
StateHistory.collectHistory = collectHistory;
}
if (collectHistory !== undefined) {
StateHistory.storeHistoryItems = storeHistoryItems;
}
ServiceLocator.injector = injector;
stateHistory.init(initialState);
routerState.init();
if (!isProd) {
(<any>window).state = StateHistory;
}
}
}
darin-cardin
commented
6 years ago @vytautas-pranskunas- I know what you mean. the AOT team seems to be in denial about the scope of the bug issue. One time, a legitimate issue was raised, and the bug was closed, with the comment "Thats the way it works". If you dont have the time or resources to fix the issue, i understand. But to just close it, when many people report the same thing.
vksgautam1
commented
6 years ago i too have same issue typescript error Error encountered resolving symbol values statically. Expression form not supported (position 90:18 in the original .ts file), resolving symbol AppModule in E:/Working Project/ngo/src/app/app.module.ts
viniciusrs
commented
6 years ago I'm trying using a subject on my route and it's cause the same issue.
export function subject() {
return new Subject<string>();
}
@NgModule({
imports: [
RouterModule.forChild([
{
path: 'services',
data: { breadcrumb: 'Our Services' },
children: [
{ path: '', pathMatch: 'full', component: ServicesComponent, data: { breadcrumb: null } },
{ path: ':slug', component: ServiceComponent, data: { breadcrumb: subject() } },
]
},
])
]
})
export class ServicesRoutingModule { }
karthik473
commented
6 years ago I also met with the same issue has anybody resoved this type of issue when running in (ng build --prod ) my angular version is 4 ERROR in Error: Error encountered resolving symbol values statically. Reference to a local (non- exported) symbol 'myDpStyles'. Consider exporting the symbol (position 9:7 in the original .ts file), resolving symbol MyDatePicker in D:/User/Karthik/test/07thaptilangular/AngularClient/node_modules/angular4-datepicker/src/my-date-picker/my-date-picker.component.ts
Sai-Maha
commented
5 years ago Hi , did anybody find the solution for that , i too get the same issue. It is strange we can able to run it when we run as "ng build --env=prod". But facing issue with ng build --prod. Are they both same .
angular-automatic-lock-bot[bot]
commented
5 years ago This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
OS?
Versions.
Repro steps.
package.json file
The log given by the failure.
ng build 10% building modules 3/3 modules 0 active(node:24869) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56 parseQuery() will be replaced with getOptions() in the next major version of loader-utils. Hash: aadb17976632b415a446
Time: 23846ms chunk {0} main.bundle.js, main.bundle.js.map (main) 180 kB {2} [initial] [rendered] chunk {1} styles.bundle.js, styles.bundle.js.map (styles) 194 kB {3} [initial] [rendered] chunk {2} vendor.bundle.js, vendor.bundle.js.map (vendor) 5.22 MB [initial] [rendered] chunk {3} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]
ERROR in Error encountered resolving symbol values statically. Calling function 'FlexLayoutModule', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule in /home/glamstudios/mobilesite/src/app/app.module.ts, resolving symbol AppModule in /home/glamstudios/mobilesite/src/app/app.module.ts
Mention any other details that might be useful.