Update node-eval to the latest version 🚀

[greenkeeper]

Version 2.0.0 of node-eval was just published.

Dependency	node-eval
Current Version	1.1.1
Type	devDependency

The version 2.0.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 node-eval.

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.

---

Release Notes

v2.0.0 (2017-11-12)

• Removed support for Node.js v0.10 and v0.12 (@blond #33).
• Updated docs (@blond #35).

Commits

The new version differs by 20 commits.

• 8f24aa9 docs: fix filename example
• 03ef74d 2.0.0
• 2d7b5f4 chore(package): changelog for v2.0.0
• 16d52b8 Merge pull request #35 from node-eval/docs
• d5f3a3a docs: update readme
• 1173804 chore: prevent package-lock.json
• 6d94545 Merge pull request #34 from node-eval/chore
• 7471a18 refactor: fix lint
• 179b37f chore(package): use eslint
• 84d6e25 docs(badges): use master branch
• 638bb96 chore(ci): run tests in master only
• 148f354 chore(package): use files field
• 96c6f4a Merge pull request #33 from node-eval/node4+
• cd9aed3 chore(pacakge): update package-lock
• c2c6edd refactor: use ES2015

There are 20 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴