The version 0.58.0 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 rollup.
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.
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.58.0 of rollup was just published.
The version 0.58.0 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 rollup.
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 556 commits.
5f0bed80.58.006f2069Fix lint errorbff9955Merge branch 'preserve-hidden-classes'f942d6eRevert most of the source-map update as there the new version contains30928f9Update source-map dependencyabf8218Add proxy layer to prevent direct module or graph access from the ast.b75ac43Use a "dirty" flag when including variables instead of handling return2f494c4Make sure initialise is all that is necessary to reset a node so that in3e1c6fcMake sure Program nodes are really only included if they have an effect93f75b6Streamline some remaining forEach and some loops67e4080Only start another tree-shaking pass if a variable was included;52fb2d7Make Program a fully functional ast node that will even receive ana903b28Take the module from the parent to avoid a constructor argument4978d7cClean up variables339f5abInitialise variables that are not initialised during constructionThere are 250 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: