This repository was archived by the owner on Aug 7, 2021. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 40
Different relative paths for lazy route files #372
Labels
Comments
@vchimev do you have an estimation for the fix? Our app is going to production soon, and we need it to plan accordingly. |
@NickIliev when can we expect a fix for this? |
@Smiley01987 @mxth the issue can now be resolved by providing an app alias in tsconfig.json (note the alias in paths
and then in the nested routing table use the alias as follows
With the above configuration, the application will build and run as expected with and without Webpack. |
The creation of the alias will be added out-of-the-box with nativescript-dev-typescript with this PR |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Expected
Nested routes resolve child modules correctly with or without
--bundle
.Current
--bundle
, the path is relative to./app
directory.--bundle
, the path is relative to the current directory of the route file.Reproduce
tns run ios
tns run ios --bundle
The text was updated successfully, but these errors were encountered: