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.
Description of the Change
Now it is possible to tell
amber watch
to not to run npm process usingapi_only
option.api_only
is a term borrowed from Rails' configuration. It might be reused in future for other API-specific functionality.Related Amber recipe: amberframework/recipes#33
Alternate Designs
Something like
no_npm
option in.amber.yml
might be used as well, although I findapi_only
more common and extendible in the future.Also
--no-npm
argument foramber watch
could be used but I find it unintuitive to use and this way we have some cli options in.amber.yml
and some as arguments and this is inconsistent.Benefits
User is able to run
amber watch
without npm dependency.Possible Drawbacks
+1 another cli option to maintain.