restructure repo and publish to npm #71
Open
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
This was
linked to
issues
Feb 8, 2024
angusfretwell
force-pushed
the
npm-package
branch
from
47ee200
to
42cb999
Compare
angusfretwell
force-pushed
the
npm-package
branch
from
42cb999
to
6e5f865
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.
As requested in #14 and #66, set this repo up for releases and publishing to NPM.
I also made a few general improvements
Once this is merged I'll publish the first release per instructions in README.md.
Since there was some restructuring involved, it'll be easier to review by looking at 6e5f865 to see the changes separately from moving the files.