Added build:all and install-all scripts#117
Merged
Merged
Conversation
3608b4b to
4746fae
Compare
mudetroit
previously approved these changes
Feb 29, 2024
Contributor
mudetroit
left a comment
There was a problem hiding this comment.
This works for now, later if we get a real monorepo going that tooling should take over.
e85594b to
a429713
Compare
mudetroit
approved these changes
Feb 29, 2024
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
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
This PR adds two tiny scripts:
build:allbuilds the library and taps into a new scripts which iterates through each directory in the examples directory to build every project../scripts/install-all.ts [ci]is a script that npm installs/ci the library and iterates through each example and does the same.The CI workflow has been updated to use this, and a new non-cache job was added to make sure
npm installdoesn't stop working due to a badpackage.json. See: #115.Type of change
Checklists
Development
Code review