upgrade dependencies #35
Open
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.
Running
npm installon master branch gives 6 deprecation warnings and 33 security vulnerability alerts. This PR resolves those by upgrading dependnecies, notably thetapdependency.Running
npm run buildon master branch prompts to installunbuildandcpy-cliinto~/.npm/_npx, and these installations give 2 more deprecation warnings. This PR moves those dependencies intodevDependenciesinstead of managing system/user-wide installations so that the package-lock mechanism andnpm auditcan stay on top of the deprecations. This PR does not resolve those two deprecation warnings, because the latest version ofunbuildstill hasn't fixed them yet.The latest version of
tapgives a warning that theclassicreporter is no longer supported, and it fallsback to "raw TAP", which is very verbose. Using the defaultbasereporter seems pretty close to the old formatting:Old output (classic):
New output (base):
This PR also commits the
package-lock.jsonfile, as per the official recommendation.This PR also adds a few directories generated by the build and test procedures to
.gitignore.This PR also upgrades the
prettierdependency, but I don't think that matters. There weren't any warnings for the old version, and the formatting produced by the two versions is identical for this codebase.