ms

2.1.3 · 8 Dec 2020MIT721.2M / weekRepository Homepage npm Atom feed

Upgrading ms From 0.1.0 to 0.2.0

Same major only

1 release in betweenevery note read

Other targets from 0.1.0Newest 0.x0.7.3 Clears its 2 advisories2.0.0 Latest2.1.3

0.1.0yours
0.2.0target

0
changes to make: 0
advisories fixed: 6
new: 0
fixes

Security

2 advisories still affect 0.2.0

Regular Expression Denial of Service in mshigh · GHSA-3fx5-fwvr-xrjg
Vercel ms Inefficient Regular Expression Complexity vulnerabilitymoderate · GHSA-w9mr-4mfr-499f

Upgrading to 2.0.0 clears them.

Release by release

0.2.0
3 Sep 20126 new
- new
  Add component.json [visionmedia]
- new
  Add days support [visionmedia]
- new
  Add hours support [visionmedia]
- new
  Add minutes support [visionmedia]
- new
  Add seconds support [visionmedia]
- new
  Add ms string support [visionmedia]

1 other line we could not sort, mostly version bumps

Refactor tests to facilitate ms(number) [visionmedia]
0.2.0

Upgrade to 0.2.0

npm install ms@0.2.0

What 0.2.0 needs

Reading 0.2.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 0.2.0. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
2 advisories still affect 0.2.0.