COMPASS-261: Automatically recompile when changes saved to source #669
Conversation
This file contains 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
|
Was rebased in #670 closing this pull. |
imlucas
changed the title
imlucas
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 removes the need for the
COMPILE_CACHE=falseenvironment variable for the .jsx, .md, and .jade files to be recompiled in development mode when a change is detected. Simply runnpm startas normal and if a change to any of these files happens, the compile cache will detect it and remove the cached version. This forces a recompile on refresh. (You will still need to CMD+R but only 1 file will recompile instead of everything like before.)This has no affect on production - files are not watched in that mode, only in
development.