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
Can't resolve an absolute path of appComponents on Windows #573
Labels
Comments
vchimev
added a commit
that referenced
this issue
Jun 21, 2018
vchimev
added a commit
that referenced
this issue
Jun 21, 2018
vchimev
added a commit
that referenced
this issue
Jun 22, 2018
vchimev
added a commit
that referenced
this issue
Jun 22, 2018
This was referenced Jun 23, 2018
vchimev
added a commit
that referenced
this issue
Jun 23, 2018
vchimev
added a commit
that referenced
this issue
Jun 25, 2018
vchimev
added a commit
that referenced
this issue
Jun 25, 2018
vchimev
pushed a commit
that referenced
this issue
Jun 26, 2018
…ws (#578) * fix: resolve appComponents absolute paths on Windows Fix #573. * fix: resolve xml namespaces absolute paths on Windows * chore(JavaScriptApp): add webpack.config.js file Clean up npm scripts. * test(JavaScriptApp): extend android application * test(JavaScriptApp): extend android activity * chore(TypeScriptApp): add webpack.config.js file Clean up npm scripts. * chore(TypeScriptApp): add platform declarations * test(TypeScriptApp): extend android application * test(TypeScriptApp): extend android activity * chore(AngularApp): add webpack.config.js file Clean up npm scripts. * chore(AngularApp): add platform declarations * test(AngularApp): extend android application * test(AngularApp): extend android activity * chore(AngularApp): update @angular/compiler-cli version * refactor(demos): minor tweaks * chore(JavaScript): remove unused variables * refactor: address comments * chore(e2e): update application activity to launch * refactor: remove tns-platform-declarations dependency * chore(e2e): remove application activity from capabilities The nativescript-dev-appium plugin gets it automatically, no need to declare it in the `appium.capabilities.json` file.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Checklist
Tell us about the problem
An absolute path added to appComponents in the
webpack.config.js
file can't be resolved during bundling on Windows.As a workaround, a relative path could be used, however, then the added components will be included in the
bundle.js
instead of thevendor.js
file.Example: HERE.
Output:
Local environment
Project data
The text was updated successfully, but these errors were encountered: