Work around an issue with webpack's extension resolution.

Not resolving ../utils imports.
This commit is contained in:
Hristo Deshev
2017-03-20 14:48:14 +02:00
committed by Hristo Deshev
parent fe54ac6ead
commit 9d67e44cdf
2 changed files with 6 additions and 2 deletions

View File

@@ -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";

View File

@@ -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";