package.json updates, fix typos in README.md and add some missing type annotations tsc was complaining about
#106
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
node-version
…dress npm vulnerabilities of some of its transient dependencies
…pt services was complaining they were undefined
|
Note: I chose node v16 for You may have some feedback for |
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.
See commit comments.
package-lock.jsonwas out of date. And I noticed somenpm auditvulnerabilities and some outdated packages. So I made updates.README.mdI just noticed (after the fact) that you have a bunch of PRs created by
botthat were probably automated. I think it is better to take this PR because I did the updates carefully by hand with a combination ofnpm installandnpm audit fix...