An in-range update of should is breaking the build 🚨

[greenkeeper]

Version 11.2.1 of should just got published.

Branch	Build failing 🚨
Dependency	should
Current Version	11.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As should is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 1 commits .

• 52b984f Fix .match(RegExp) for everything not supported

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

Version 12.0.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

Better Map Set equality

Map/Set/WeakMap/WeakSet equality checks

User @BridgeAR pointed to a number of bugs and inconcistency in Map/Set/WeakMap/WeakSet checks. To fix all this things, i switched map and set equality checks to do key checks defined in standard instead of value checks.
Typical example that was working before this release:

const m1 = new Map([[{ a: 1 }, 11]]);
const m2 = new Map([[{ a: 1 }, 11]]);
m1.should.be.eql(m2)

And not this example is breaking. At first view it is a bit unclear why it should not be so. Consider another example:

const m1 = new Map([[{}, 11], [{}, 12]]);
const m2 = new Map([[{}, 11], [{}, 12]]);
m1.should.be.eql(m2)

This example is not that clear if it should assert or not, right? (it should).

As Map and Set (as their weak equavalents) allows to use any type value/ref as key, perfectly equal by value (what should.js do) {} and {} is not equal by reference. In should.js i am always trying to limit users to do not shoot themselfs in their foots and just do right thing if possible and when possible. That is why both examples will throw assertions starting 12.0.0.

Consistency in bundles

For the long time (probably several years now) browser bundle and node bundle has little differences in globals.
To make them sync i am doing such changes to bundles:

1. Browser bundle will not contain window.Should any more (with capital S). It was deprecated for the long time. Just use window.should as is.
2. Node bundle change global.should to be should function instead of getter attached to Object.prototype.

Commits

The new version differs by 12 commits.

• 52dc121 Release 12.0.0
• 6c1e6bd Prettier all
• 6114e76 Update years
• 670df30 Merge branch 'master' of github.com:shouldjs/should.js
• ecf8033 Update tools
• e4d0acc Normalize entry points
• f4adabb Set zuul to use 2 last versions of browsers
• 8114b5d Merge pull request #143 from isayme/issue/aboveOrEqual-belowOrEqual
• 02ec6a0 fix error message for aboveOrEqual & belowOrEqual
• 031888e Merge pull request #140 from carldunham/feature/cd/add-equals-eqls
• 1e4909b Add for readability: equals, eqls
• 4a53d94 Release 11.2.1

See the full diff

[greenkeeper]

Version 13.0.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 11 commits.

• b9bf8ff Release 13.0.0
• c8a5851 Remove ignored file
• ebfdd19 Travis uses node 8
• 92d0db1 Remove bower, as it seems nobody uses it
• fe1ae5c Fix shouldjs/should.js#150
• c4924be Fix build and restore old files. In a bit silly way, but it works.
• c946259 Fix tests
• 90bf91e Prettier everything
• 999b122 Add first version of TS typings for should.js
• 06062c5 Reorganize build
• c50e66a Disable package-lock.json because i am controlling all dependencies

See the full diff

[greenkeeper]

Version 13.0.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

13.0.1

Add back missing umd build in root of package

Commits

The new version differs by 2 commits.

• e90c2cf Release 13.0.1
• 789b8cf Add missing umd bundle

See the full diff

[greenkeeper]

Version 13.1.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

13.1.0

New

1. Now all zero argument assertions throw TypeError in case any argument passed to them.
2. Aliased .fulfill/.fulfilledWith to .resolve/.resolvedWith`

Fixes

1. TS definition fixed to allow such imports:

import should from 'should';

Commits

The new version differs by 6 commits.

• c807e9d Release 13.1.0
• 8acfba1 Merge pull request #154 from citizensas/master
• c12afd0 chore: should has no default export
• 4a846b1 Fill history
• f5c9cc3 Added check for zero argument assertions.
• fe6b136 Added .resolved, .resolvedWith as aliases to .fulfilled, .fulfilledWith

See the full diff

[greenkeeper]

Version 13.1.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

• f8ab675 Release 13.1.1
• e65ccf0 Add missing return type

See the full diff

[greenkeeper]

Version 13.1.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

• ff0877a Release 13.1.2
• 6c8cb39 Revert typings to use = instead of default export. Fixes #155

See the full diff

[greenkeeper]

Version 13.1.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

13.1.3

Fix #157

Commits

The new version differs by 5 commits.

• cc2f68b Release 13.1.3
• 76ed8ce Merge pull request #160 from shouldjs/deps
• 1e7b1d0 Merge pull request #159 from shouldjs/fix-157
• 82c1683 Update deps
• 6a7989f Fix #157

See the full diff

[greenkeeper]

Version 13.2.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 3 commits.

• 7095ae5 Release 13.2.0
• bcf4588 Update build
• 120e3d9 Add test for Set.containEql

See the full diff

[greenkeeper]

Version 13.2.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

• 9748ae6 Release 13.2.1
• 70733b9 Fix .size with should as function

See the full diff

[greenkeeper]

Version 13.2.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 9 commits.

• 031b8e6 Release 13.2.2
• 6db456c Merge branch 'master' of github.com:shouldjs/should.js
• 1ab1661 Add note about TS
• 889e22e Merge pull request #171 from jsoref/spelling
• 79ec809 Spelling fixes
• 0abf2d5 Merge pull request #167 from lumaxis/bugfix/typescript-error
• d1e9efe Fix TypeScript compiler issue with fulfilled assertion
• 9dcde0f Merge pull request #164 from chris-grabcad/UpdateDefinitionsOfTrueAndFalseInTypings
• 7917c9c Add optional message to [Tt]rue and [Ff]alse so they can be used in typecript tests

See the full diff

[greenkeeper]

Version 13.2.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

• 38910f7 Release 13.2.3
• 40db606 Do not use getter internally

See the full diff