The version 0.7.3 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of source-map.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
1ea5ee3First stab at classes. source-map-consumer is a mess in order to keep the API the same. That file needs careful review. Everything else is pretty straightforward. Fixes #334. Fixes #259.
adfd0fbMerge pull request #335 from hildjj/coverage
39db032Add code coverage instructions to CONTRIBUTING.md
3f2b104Add support for coverage metrics with nyc and coveralls. Coveralls integration will need to be turned on.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 0.7.3 of source-map was just published.
source-mapThe version 0.7.3 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of source-map.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 132 commits.
b2171d5Bump to version 0.7.386d2f30Merge pull request #336 from hildjj/classes14de5f8Address comments in code review1ea5ee3First stab at classes. source-map-consumer is a mess in order to keep the API the same. That file needs careful review. Everything else is pretty straightforward. Fixes #334. Fixes #259.adfd0fbMerge pull request #335 from hildjj/coverage39db032Add code coverage instructions to CONTRIBUTING.md3f2b104Add support for coverage metrics with nyc and coveralls. Coveralls integration will need to be turned on.df6608dMerge pull request #332 from hildjj/lint73f5d1aSwitch to let/const from varbf025a8Apply the Firefox eslint rules, minus the Firefox-specific plugins.8214089Merge pull request #330 from ds300/fix/callback-stackb87dfc8update dist121d627keep callbacks on stack to allow nested consumer usageb93aadbadd failing test for nested consumer usagec1e2ec8Merge pull request #329 from wizawu/masterThere are 132 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: