Update basic packages and testing packages #20
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.
Y'all know what this is about. No JIRA ticket for this.
Bunch of various things needed fixing beyond the package updates, so I've included them here just because:
istanbultonycsince the former is deprecated (with a security vulnerability warning in a child package)mochaso had to include auseUnifiedTopologyflag in the default connectionyarn test:coverageandyarn test:check-coveragework (previously they failed to callyarn pretestproperly)SECURITY VULNERABILITIES RESOLVED:
For the record, you can check what child packages belong to parent packages by doing
npm ls ${childPackage}mongoosedebugsince we weren't using it (nor wasnycusing it)nychas an updatedhandlebarsthereby satisfying the version requirementeslintmochasatisfies version requirement fordiffeslint-watchsatisfies version requirement forbracescommitizen,mocha,coveralls, and addingnycsatisfied version requirements forjs-yamlcoverallssatisfies version requirement fortunnel-agentfstreamremoved (was a child of one of the packages I removed)tarremoved (was a child of one of the packages I removed) -- current child frombcryptis well above the minimum required version (min req:2.2.2, current remaining:4.4.10)express-validationsatisfied child version oflodashexpress-winston, but moving from v2 to v4 requires a Winston migrationcommitizenversion has child version oflodashat4.17.14which puts it under the required version4.17.15-- look into using an alternative (which is another migration)supertestversion has child version ofextendat3.0.0which puts it under the required version3.0.2-- consider only usingsupertest-as-promisedinstead or simplyrequestcommitizensatisfies minimum required version formergeExtraneous (not sure what to do about these...):
stringstreamis-my-json-valid