Bump faustwp/cli to 0.1.5 #101
Merged
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
So that new FAUST_NO_INTERACTION env vars work when starting sites from a blueprint in Local.
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.
So that new
FAUST_NO_INTERACTIONenv vars work when creating Faust.js sites from a blueprint in Local.Context
The
@faustwp/clipackage introduced aFAUST_NO_INTERACTIONenv var in 0.1.5 at wpengine/faustjs#1162. It allows unsupervised installation of Faust without a user prompt to accept/decline telemetry.The Local Atlas add on runs npm install in this blueprint's directory when the site is first cloned.
Without this version bump to 0.1.5, faustwp/cli 0.1.4 gets installed during blueprint setup. This means the new
FAUST_NO_INTERACTIONenv var is ignored and the node server never gets beyond the telemetry prompt.