Update should to the latest version 🚀 #4
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 13.0.1 of should just got published.
The version 13.0.1 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of should.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
13.0.1Add back missing umd build in root of package
Commits
The new version differs by 13 commits.
e90c2cfRelease 13.0.1789b8cfAdd missing umd bundleb9bf8ffRelease 13.0.0c8a5851Remove ignored fileebfdd19Travis uses node 892d0db1Remove bower, as it seems nobody uses itfe1ae5cFix shouldjs/should.js#150c4924beFix build and restore old files. In a bit silly way, but it works.c946259Fix tests90bf91ePrettier everything999b122Add first version of TS typings for should.js06062c5Reorganize buildc50e66aDisable package-lock.json because i am controlling all dependenciesSee 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 🌴