[TypeScript & Vue project] When using --bundle changes made to a platform specific file in node_modules does not start a new build process
#4480
Comments
Fatme
changed the title
--budnle changes made to a platform specific file in node_modules does not start a new build process--bundle changes made to a platform specific file in node_modules does not start a new build process
VladimirAmiorkov
changed the title
--bundle changes made to a platform specific file in node_modules does not start a new build process--bundle changes made to a platform specific file in node_modules does not start a new build process
Fatme
added a commit
to NativeScript/nativescript-dev-webpack
that referenced
this issue
May 31, 2019
Fatme
added a commit
to NativeScript/nativescript-dev-webpack
that referenced
this issue
Jun 5, 2019
Fatme
added a commit
to NativeScript/nativescript-dev-webpack
that referenced
this issue
Jun 6, 2019
Fatme
added a commit
to NativeScript/nativescript-dev-webpack
that referenced
this issue
Jun 10, 2019
Fatme
added a commit
to NativeScript/nativescript-dev-webpack
that referenced
this issue
Jun 12, 2019
Fatme
added a commit
to NativeScript/nativescript-dev-webpack
that referenced
this issue
Jun 15, 2019
rosen-vladimirov
pushed a commit
to NativeScript/nativescript-dev-webpack
that referenced
this issue
Jun 19, 2019
* fix: don't provide fake paths to the {N} CLI - relative to the `app` folder
* feat: remove not needed hooks
* feat: remove webpack compiler logic
* fix: don't copy app_resources to the platforms folder
* fix: respect --env.verbose
* feat: respect production mode based on release option
Implements: #911
* fix: watch platform specific files from node_modules
Rel to: NativeScript/nativescript-cli#4480
* fix: don't emit absolute webpack's runtime files
Previously we needed to emit files with full paths as {N} CLI relies on this and expected them in a such format. With the changes for "webpack-only" mode, {N} CLI expects only relative paths. So we need to fix this in order to ensure that runtime.js file will not be transferred on device on change in hmr mode.
* fix: don't process runtime.js files
We needed a special processing for `runtime.js` files as we excluded them when transferring the files on device. As the CLI is filtering and emit only hot-update files we don't need this logic anymore.
* fix: emit runtime files and entry point files
* fix: update webpack config files of demo apps
* fix: don't use short imports in demo apps
* fix: update dependencies of demo apps so they are compatible with 6.0 release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Provide version numbers for the following components (information can be retrieved by running
tns infoin your project folder or by inspecting thepackage.jsonof the project):Describe the bug
When developing an NativeScript plugin and using the following workflow, any changes to the .ts files of the developed plugin do not trigger sync to the device:
Workflow:
srcfolder which hold the plugin's source codetns plugin add ...tns run ios --bundleTo Reproduce
Use the above workflow with any plugin that is created from the plugin-seed like nativescript-picker, run its demo and make a change in the picker.ios.ts file.
Expected behavior
Doing the above should force a webpack build and a refresh of the app in the simulator/device without full build (a.k.a a live sync).
Sample project
A demo project can be found here, use the above workflow to build it.
The text was updated successfully, but these errors were encountered: