chore: add build scripts #139
Merged
Conversation
This file contains hidden or 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
smeijer
force-pushed
the
feature/buildscripts
branch
from
18f62c4 to
b0f6966
Compare
smeijer
force-pushed
the
feature/buildscripts
branch
from
b0f6966 to
da59424
Compare
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.
I've created a few build scripts. Although it looks like I added some complexity, I think this is better maintainable in the long term.
ZeroConfig in package.json looks nice, but adding arguments to a cli tool, is also some form of configuration.
At least now the
packageJson#scriptsare clean and clear, and the build process is understandable.