Update reify to the latest version 🚀

[greenkeeper]

Version 0.11.0 of reify just got published.

Dependency	reify
Current Version	0.10.0
Type	devDependency

The version 0.11.0 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 reify.
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.

---

Commits

The new version differs by 29 commits0.

• cfc5d2f Bump NPM version to 0.11.0 in preparation for publishing.
• 5e31f77 Rename module.runModuleSetters to just module.runSetters. (#160)
• 2c78577 Update README.md to describe the new module.watch(require(id), ...) strategy.
• a61d310 Use module.watch(require(id), ...) to avoid calling module.require.
• dd2db15 Remove unused Module.prototype reference from compile-hook.
• 60c9301 Remove unused SemVer from compile-hook and wrapper.
• 62238cd Memoize maxSatisfying for a perf win.
• 716e4d1 Fix node range.
• ba12df2 Ensure the wrapper maps get the correct raw function.
• 3636139 Reuse “__reify” symbol when possible.
• 6451d45 Cleanup wrapper.
• d98d229 Move abc to misc folder.
• 867f55a Move misc tests to their own folder.
• fdac8a7 Move import tests to their own folder.
• 78f3de5 Move compiler tests to their own folder.

There are 29 commits in total.

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 🌴