feat: allow additional standard dependencies in .env
#109
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
See #104. This allows additional standard dependencies to be specified in the `.env` file under the `STANDARD_DEPENDENCIES` variable.
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.
Following a discussion in #104, this PR adds
peg:oops-modto the standard dependencies, and also allows you to specify additional ones as a comma-separated list in a variableSTANDARD_DEPENDENCIESin your.envfile.On top of that, it also allows you to specify the default variants with
STANDARD_VARIANTS. That way you don't always have to specify the different variants manually when runningnpm run sc4pac.Example
.envfile:cc @noah-severyn