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
Allow user to configure
amber watch
from.amber.yml
. Configuring this way is optional (there is still a default config, and it is the same as before), and you can continue to use the command line switches if you want (if you have a config in.amber.yml
, command line switches will override it).A sample
.amber.yml
:Alternate Designs
The config is too complex to configure solely via command line switches/arguments, and leaving it non-user-configurable is creating unhappiness among users.
Benefits
Developers are now free to choose
yarn
overnpm
, or even nothing at all. Additionally, they can useamber watch
to run other processes as well.Possible Drawbacks
Mainly some code bloat. It's certainly possible that this is not something the amber project should handle directly.