This repository was archived by the owner on Aug 7, 2021. It is now read-only.
fix-next(HMR): resolve correctly modulePath in hot loaders #781
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use
this.rootContext
instead ofthis.context
.For example this second-page module:
--->
this.resourcePath
is /Users/vchimev/git/nativescript-dev-webpack/demo/TypeScriptApp/app/views/second-page.xml--->
this.context
is /Users/vchimev/git/nativescript-dev-webpack/demo/TypeScriptApp/app/views--->
this.rootContext
is /Users/vchimev/git/nativescript-dev-webpack/demo/TypeScriptApp/app--->
modulePath
should be ./views/second-page.xmlPR Checklist
What is the current behavior?
For example, this second-page module resolves
modulePath
to./second-page.xml
.What is the new behavior?
From the above example,
modulePath
should be./views/second-page.xml
.