List build tools under devDependencies #529
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi!
This PR moves the build tools into devDependencies. Right now, if someone installs this repo in another JS project (for example with
npm install git+https://github.com/cavi-au/Consent-O-Matic.git#{tag}), npm also pulls in all the build tools, which can be a bit inconvenient.With this change, that command will only bring in the repo itself. That makes it easier to reuse the core logic and rules in other projects beyond the official browser extensions.
The only small adjustment needed is when building locally or in GitHub Actions: dependencies should be installed with npm install --include dev or npm ci --include dev.
Thanks a lot for considering this!