Update requirements in readme

packages/node-resolve/README.md

@@ -13,7 +13,7 @@
 
 ## Requirements
 
-This plugin requires an [LTS](https://github.com/nodejs/Release) Node version (v8.0.0+) and Rollup v1.20.0+.
+This plugin requires an [LTS](https://github.com/nodejs/Release) Node version (v10.0.0+) and Rollup 2.78.0+.
 
 ## Install
 
@@ -75,14 +75,7 @@ If `true`, instructs the plugin to use the browser module resolutions in `packag
 Type: `Array[...String]`<br>
 Default: `['node_modules']`
 
-A list of directory names in which to recursively look for modules.
-
-### `modulePaths`
-
-Type: `Array[...String]`<br>
-Default: `[]`
-
-A list of absolute paths to additional locations to search for modules. [This is analogous to setting the `NODE_PATH` environment variable for node](https://nodejs.org/api/modules.html#loading-from-the-global-folders).
+One or more directories in which to recursively look for modules.
 
 ### `dedupe`
 
@@ -221,7 +214,7 @@ export default ({
 })
 ```
 
-## Resolving Require Statements
+## Resolving require statements
 
 According to [NodeJS module resolution](https://nodejs.org/api/packages.html#packages_package_entry_points) `require` statements should resolve using the `require` condition in the package exports field, while es modules should use the `import` condition.