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
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…revent the app to be prepared after snapshot generation
…ucture Vlaeva/refactor project structure
ts |
…snapshot Vlaeva/postinstall replace snapshot
sis0k0
approved these changes
Jun 13, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR introduces support for generating a v8 heap snapshot for a random webpack bundle on linux and mac. Snapshot generation is enabled by adding
--snapshot
flag at the end of thens-bundle
command inpackage.json
. This will add theSnapshotWebpackPlugin
to the webpack configuration. TheSnapshotWebpackPlugin
receives a bundle name as a parameter.The generated snapshots are included in the app in the form of binary files (the default option) or native libraries. The second option requires having a local copy of the Android NDK required for building the libraries.