Skip to content

chore: merge release in master #4799

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 22 commits into from
Jul 3, 2019
Merged

chore: merge release in master #4799

merged 22 commits into from
Jul 3, 2019

Conversation

rosen-vladimirov
Copy link
Contributor

PR Checklist

What is the current behavior?

What is the new behavior?

Fixes/Implements/Closes #[Issue Number].

Fatme and others added 22 commits June 30, 2019 23:31
…gular app with uglify option

Currently CLI has a logic to restart the application when one or more of the emitted files from webpack compilation is not hot update. When a lazy loaded code is changed in angular application and uglify option is provided, CLI always restarts the application. (as 0.js, 1.js are reported as changed). This happens due to the fact that CLI omits entry point files and runtime files from emitted files to check if all rest files are hot updates. As the lazy loaded chunks (`0.js`, `1.js`) are neither entry point files nor runtime files, they are not omitted and CLI decides that there is file that is not hot update and restarts the application. This PR changes this behavior and respects only chunk files from webpack compilation. Chunk files are all files except hot update files. Chunk files are: `runtime.js`, `tns_modules/inspector-modules.js`, `bundle.js`, `vendor.js` and all lazy loaded modules.
Currently deploy command doesn't release the console as the watch option has default true value.
Currently CLI respects the changes only in the followings package.json files:
 * package.json from app folder
 * package.json from root folder of the application
The changes from package.json files form NS plugins are not respected as they are not added to the watch's patterns.
Currently when prepare command is executed from plugin's directory, CLI throws an error that it is not able to find `webpack.config.js` file. This is due to the reason that CLI finds nativescript key in package.json and consider that directory as project dir. This PR fixes this behavior as checks if there is `id` inside nativescript key.
…ge-json

fix: add package.json files from nativescript plugins to watch patterns
fix: release the console on deploy command
…gins-dir

fix: fix prepare from plugin's directory
In some cases (for example `tns preview` and scan QR code simultaneously with several devices) we start multiple watchers per platform. We should always have single watcher per platform (one from webpack and one native in fact).
Handle preview initial sync once per device (in some cases PubNub reports the device multiple times). Also prepare all the files once per platform, not per each device.
…sions

fix: update dependencies to latest rc versions
…-files

fix: set the proper root for the auto-generated files glob matching
Currently when stop method is called with empty array, the livesync process is stopped for all devices but the runOnDeviceStopped event is not emitted. This PR fixes this behavior as ensures the runOnDeviceStopped event will be emitted for all connected devices.
…version

refactor(migrate): bump the version of {N} vue to 2.3.0-rc.1
fix: fix stop run on device when the method is called with empty array
fix: don't restart application when lazy loaded code is changed in angular app with uglify option
fix: update the version of nativescript-dev-webpack plugin on migrate command
@rosen-vladimirov rosen-vladimirov self-assigned this Jul 3, 2019
@cla-bot cla-bot bot added the cla: yes label Jul 3, 2019
@Fatme Fatme merged commit 946dda4 into master Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants