This repository was archived by the owner on Aug 7, 2021. It is now read-only.
fix-next: cache package.json, starter.js and tns-java-classes.js between compilations #444
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
Mitko-Kerezov
approved these changes
Feb 27, 2018
MartoYankov
approved these changes
Feb 27, 2018
sis0k0
changed the title
|
test |
sis0k0
force-pushed
the
vlaeva/cache-start-modules
branch
from
bb8f487 to
24fe12e
Compare
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.
The starter assets shouldn't be emitted on each compilation cycle, when using webpack with watch. Instead they should be cached if possible.