Update deps

[job13er]

This project uses semver, please check the scope of this pr:

• #none# - documentation fixes and/or test additions
• #patch# - backwards-compatible bug fix
• #minor# - adding functionality in a backwards-compatible manner
• #major# - incompatible API change

CHANGELOG

Security

• Update yarn.lock and bump mkdirp to resolve some dependabot warnings

[job13er]

I did see the following in the console when the tests were run:

["@babel/plugin-proposal-private-property-in-object", { "loose": false }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "true" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "false" for @babel/plugin-proposal-private-property-in-object.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
	["@babel/plugin-proposal-private-methods", { "loose": false }]
to the "plugins" section of your Babel config.

I don't know if that was already there or not though.

[sandersky]

I did see the following in the console when the tests were run:

["@babel/plugin-proposal-private-property-in-object", { "loose": false }]

to the "plugins" section of your Babel config.

Though the "loose" option was set to "true" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "false" for @babel/plugin-proposal-private-property-in-object.

The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding

	["@babel/plugin-proposal-private-methods", { "loose": false }]

to the "plugins" section of your Babel config.

I don't know if that was already there or not though.

I've seen that in the past but I don't recall if that was this project or another one. Shouldn't be a blocker though.

[job13er]

seems like travis didn't get the hint to run the tests. Gonna try closing and re-opening

[job13er]

@sandersky It looks like maybe this project is still trying to build on travis-ci.org when that doesn't build anymore and it needs to switch to travis-ci.com.