-
Notifications
You must be signed in to change notification settings - Fork 311
RangeError: Maximum call stack size exceeded in 1.2.2. #854
Comments
@kleeb i was stuck with this error for 2 weeks, go to your package.json and find
remove it and try to build again, if you get success then try using webpack |
I have a custom extended ionic_rollup config |
any news on this one, anyone has this kind of problem with Typescript 2.2.x ? |
Can't say that I've seen this one. Are you using Angular 4? Angular 2 does not support TS 2.2. Thanks, |
You are totally right Dan. Was just checking package.json on the main ionic repo, but didn't look at angular, which is already 4.0.0. Will skip it for now and check it on ionic3 with TS2.2 and Angular4. |
The same thing on ionic 3 with Angular 4 and TS 2.2.2
package.json
|
FIX: now it turned into another error #853 |
Version 1.2.2.
Release bundle build (dev works correct, previous working 1.1.4).
Typescript 2.2.2.
Bundler: rollup
[13:54:20] rollup finished in 43.13 s
[13:54:20] sass started ...
[13:54:20] transpile bundle started ...
[13:54:42] ionic-app-script task: "build"
[13:54:42] RangeError: Maximum call stack size exceeded
RangeError: Maximum call stack size exceeded
at getTypeAtFlowBranchLabel (ionic/node_modules/typescript/lib/typescript.js:33971:46)
at getTypeAtFlowNode (ionic/node_modules/typescript/lib/typescript.js:33843:29)
at getTypeAtFlowCondition (ionic/node_modules/typescript/lib/typescript.js:33937:32)
at getTypeAtFlowNode (ionic/node_modules/typescript/lib/typescript.js:33832:32)
at getTypeAtFlowBranchLabel (ionic/node_modules/typescript/lib/typescript.js:33983:36)
at getTypeAtFlowNode (ionic/node_modules/typescript/lib/typescript.js:33843:29)
at getTypeAtFlowCondition (ionic/node_modules/typescript/lib/typescript.js:33937:32)
at getTypeAtFlowNode (ionic/node_modules/typescript/lib/typescript.js:33832:32)
at getTypeAtFlowCondition (ionic/node_modules/typescript/lib/typescript.js:33937:32)
at getTypeAtFlowNode (ionic/node_modules/typescript/lib/typescript.js:33832:32)
The text was updated successfully, but these errors were encountered: