Work around an issue with webpack's extension resolution.

hdeshev · hdeshev · commit 9d67e44cdf64 · 2017-03-20T16:12:10.000+02:00
Not resolving ../utils imports.
diff --git a/tns-core-modules/ui/frame/frame.ios.ts b/tns-core-modules/ui/frame/frame.ios.ts
@@ -5,7 +5,9 @@ import { Page } from "../page";
 //Types.
 import { FrameBase, View, application, layout, traceEnabled, traceWrite, traceCategories, isCategorySet } from "./frame-common";
 import { _createIOSAnimatedTransitioning } from "../transition";
-import * as uiUtils from "../utils";
+// HACK: Webpack. Use a fully-qualified import to allow resolve.extensions(.ios.js) to
+// kick in. `../utils` doesn't seem to trigger the webpack extensions mechanism.
+import * as uiUtils from "tns-core-modules/ui/utils";
 import * as utils from "../../utils/utils";
 
 export * from "./frame-common";
diff --git a/tns-core-modules/ui/page/page.ios.ts b/tns-core-modules/ui/page/page.ios.ts
@@ -5,7 +5,9 @@
 } from "./page-common";
 import { ios as iosApp } from "../../application";
 import { device } from "../../platform";
-import * as uiUtils from "../utils";
+// HACK: Webpack. Use a fully-qualified import to allow resolve.extensions(.ios.js) to
+// kick in. `../utils` doesn't seem to trigger the webpack extensions mechanism.
+import * as uiUtils from "tns-core-modules/ui/utils";
 
 export * from "./page-common";
 
