readme/changelog: global installation changes

CHANGELOG.md

@@ -11,6 +11,10 @@ This project adheres to [Semantic Versioning](http://semver.org/).
   - BREAKING: Node.js 6 is no longer supported
     - Node.js 6 is EOL and will no longer be receiving security updates. As a result, the eslint team has decided to drop support for it.
     - To prevent breaking CI for projects which still support Node 6, `standard` silently passes when run by an unsupported version of Node.
+  - Plugins are no longer affected by `standard`'s location
+    - Previously, `standard` loaded plugins relative to the location of the `standard` package itself. As a result, we suggested that users with global `standard` installations should also install plugins globally, and users with local `standard` installations should install plugins locally. However, due to a design bug, this strategy caused `standard` to randomly fail to load plugins under certain circumstances, particularly when using package management tools like `lerna` and Yarn Plug n’ Play.
+    - As a rule of thumb: With `standard` 13, plugins should always be installed locally, even if `standard` was installed globally. More precisely, `standard` 13 resolves plugins relative to the end user’s project by default, and always resolves parsers relative to the location of the config file that imports them.
+    - To address: If you use a global installation of `standard` (e.g. installed with `npm install standard --global`) along with plugins, you should install those plugins and parsers locally in the projects where you run `standard`.
 
 - Update `eslint-plugin-promise` from `~4.0.0` to `~4.2.1`
 

README.md

@@ -521,10 +521,6 @@ Or, add this to `package.json`:
 }
 ```
 
-If `standard` is installed globally (i.e. `npm install standard --global`), then
-be sure to install `babel-eslint` globally as well, with
-`npm install babel-eslint --global`.
-
 ## Can I use a JavaScript language variant, like Flow or TypeScript?
 
 `standard` supports the latest ECMAScript features. However, Flow and TypeScript add new
@@ -562,10 +558,6 @@ Or, add this to `package.json`:
 
 *Note: `plugin` and `plugins` are equivalent.*
 
-If `standard` is installed globally (i.e. `npm install standard --global`), then
-be sure to install `babel-eslint` and `eslint-plugin-flowtype` globally as well, with
-`npm install babel-eslint eslint-plugin-flowtype --global`.
-
 ### TypeScript
 
 To use TypeScript, you need to run `standard` with `@typescript-eslint/parser` as the parser,
@@ -599,10 +591,6 @@ With that in `package.json`, you can run:
 standard *.ts
 ```
 
-If `standard` is installed globally (i.e. `npm install standard --global`), then
-be sure to install `@typescript-eslint/parser` and `eslint-plugin-typescript` globally as well,
-with `npm install @typescript-eslint/parser eslint-plugin-typescript --global`.
-
 ## What about Mocha, Jest, Jasmine, QUnit, etc?
 
 To support mocha in test files, add this to the top of the test files: