connect

3.7.0 · 18 May 2019MIT30.2M / weekRepository Homepage npm Atom feed

Upgrading connect From 1.9.2 to 2.0.0

Same major only

1 release in betweennotes for 0

Other targets from 1.9.2Clears its 3 advisories2.14.0 Latest3.7.0

2.0.0 has no release note on GitHub or in the repository's changelog, so its breaking changes are missing from the counts below.

1.9.2yours
2.0.0target

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

Counted from 0 of 1 release notes. Advisories are counted from the advisory database, in full.

Security

3 advisories still affect 2.0.0

methodOverride Middleware Reflected Cross-Site Scripting in connectlow · GHSA-3fw8-66wf-pr7m
Node Connect Reflected Cross-Site Scripting in Sencha Labs Connect middlewaremoderate · GHSA-6w62-83g6-rfhj
Cross-Site Scripting in connectmoderate · GHSA-rch9-xh7r-mqgw

Upgrading to 2.14.0 clears them.

Upgrade to 2.0.0

npm install connect@2.0.0

What 2.0.0 needs

Reading 2.0.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 2.0.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.
3 advisories still affect 2.0.0.