From 10c3e91d4238b97b03788f3b20cb34403681449c Mon Sep 17 00:00:00 2001 From: Kevin Partington Date: Thu, 7 Jul 2016 12:46:28 -0500 Subject: [PATCH] Docs: Remove reference from 3.0.0 migration guide (refs #6605) (#6618) --- docs/user-guide/migrating-to-3.0.0.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/user-guide/migrating-to-3.0.0.md b/docs/user-guide/migrating-to-3.0.0.md index 238480ded19..31eb4b5b863 100644 --- a/docs/user-guide/migrating-to-3.0.0.md +++ b/docs/user-guide/migrating-to-3.0.0.md @@ -13,9 +13,8 @@ With ESLint v3.0.0, we are dropping support for Node.js versions prior to 4. Nod ESLint v3.0.0 now requires that you use a configuration to run. A configuration can be any of the following: 1. A `.eslintrc.js`, `.eslintrc.json`, `.eslintrc.yml`, `.eslintrc.yaml`, or `.eslintrc` file either in your project or home directory. -2. Configuration options passed on the command line using `--rule` -3. A configuration file passed on the command line using `-c`. -4. A configuration passed to `CLIEngine` with the `useSpecificConfig` option. +2. Configuration options passed on the command line using `--rule` (or to CLIEngine using `rules`). +3. A configuration file passed on the command line using `-c` (or to CLIEngine using `configFile`). If ESLint can't find a configuration, then it will throw an error and ask you to provide one.