Upgrading should 6 to 7
Breaking6.0.3 → 7.1.1Breaking6New5Changed1Fixed6Other1
BreakingUpgrade verdict
6 breaking changes.
In plain terms
- Assertions that were accessed as properties must now be called as functions.
- Values like DOM nodes and typed arrays are now classified more precisely, which can change assertion results.
- The type reported for some values may differ from before.
- .matchEach and .matchAny now use .match internally.
Must act Top 3 of 6 that need code or config changes
Moves should-equal 0.3.1 → 0.5.0, should-format 0.0.7 → 0.3.1, should-type 0.0.4 → 0.2.0. Your build may pick other versions.
What you must change
Breaking6
Removes getter assertions; all assertions are now functions.
Makes type detection more accurate for DOM nodes and typed arrays.
Changes the result of should-type to be more accurate and consistent.
should-type.matchEach and .matchAny now use .match internally.
.matchEach.matchAny.matchRemoves the proxy returning to check property names.
should-format output now looks more like Chrome developer tools inspections.
should-format