standard - npm Package Compare versions

Comparing version 8.0.0 to 8.1.0

AUTHORS.md

@@ -70,3 +70,6 @@ # Authors
 - Morton Fox ([e-mail])
+- Jason Kurian ([e-mail])
+- Pau Ramon Revilla ([e-mail])
+- Tim Oxley ([e-mail])
 
 #### Generated by bin/update-authors.sh.

CHANGELOG.md

@@ -6,2 +6,7 @@ # Change Log
 
+## 8.1.0 - 2016-09-17
+
+- Update ESLint from 3.3.x to 3.5.x.
+- Around 10 additional rules are now fixable with `standard --fix`!
+
 ## 8.0.0 - 2016-08-23
@@ -28,7 +33,7 @@
 With `standard` v8.0.0, we are also dropping support for Node.js versions prior to
-4. Node.js 0.10 and 0.12 are in maintenance mode and will be unsupported at the end
-of 2016. Node.js 4 is the current LTS version. If you are using an older version of
-Node.js, we recommend upgrading to at least Node.js 4 as soon as possible. If you
-are unable to upgrade to Node.js 4 or higher, then we recommend continuing to use
-`standard` v7.x until you are ready to upgrade Node.js.
+v4. Node.js 0.10 and 0.12 are in maintenance mode and will be unsupported at the
+end of 2016. Node.js 4 is the current LTS version. If you are using an older
+version of Node.js, we recommend upgrading to at least Node.js 4 as soon as
+possible. If you are unable to upgrade to Node.js 4 or higher, then we recommend
+continuing to use `standard` v7.x until you are ready to upgrade Node.js.
 
@@ -35,0 +40,0 @@ **Important:** We will not be updating the `standard` v7.x versions going forward.

package.json

 {
   "name": "standard",
   "description": "JavaScript Standard Style",
-  "version": "8.0.0",
+  "version": "8.1.0",
   "author": {
@@ -15,5 +15,5 @@ "email": "[e-mail]",
   "dependencies": {
-    "eslint": "~3.3.1",
-    "eslint-config-standard": "6.0.0-beta.3",
-    "eslint-config-standard-jsx": "3.0.0",
+    "eslint": "~3.5.0",
+    "eslint-config-standard": "6.0.1",
+    "eslint-config-standard-jsx": "3.0.1",
     "eslint-plugin-promise": "^2.0.0",
@@ -20,0 +20,0 @@ "eslint-plugin-react": "^6.0.0",

README.md

@@ -68,5 +68,5 @@ <h1 align="center">
 - [Usage](#usage)
+  - [What you might do if you're clever](#what-you-might-do-if-youre-clever)
   - [Badge](#badge)
   - [Text editor plugins](#text-editor-plugins)
-  - [What you might do if you're clever](#what-you-might-do-if-youre-clever)
 - [FAQ](#faq)
@@ -80,3 +80,4 @@ - [Why would I use JavaScript Standard Style?](#why-would-i-use-javascript-standard-style)
   - [I use a library that pollutes the global namespace. How do I prevent "variable is not defined" errors?](#i-use-a-library-that-pollutes-the-global-namespace-how-do-i-prevent-variable-is-not-defined-errors)
-  - [Can I use a custom JS parser for bleeding-edge ES6 or ES7 support?](#can-i-use-a-custom-js-parser-for-bleeding-edge-es6-or-es7-support)
+  - [Can I use a custom JS parser for bleeding-edge ES next support?](#can-i-use-a-custom-js-parser-for-bleeding-edge-es-next-support)
+  - [Can I use a JavaScript language variant, like Flow?](#can-i-use-a-javascript-language-variant-like-flow)
   - [Can you make rule X configurable?](#can-you-make-rule-x-configurable)
@@ -136,2 +137,30 @@ - [What about Web Workers?](#what-about-web-workers)
 
+### What you might do if you're clever
+
+1. Add it to `package.json`
+
+  ```json
+  {
+    "name": "my-cool-package",
+    "devDependencies": {
+      "standard": "*"
+    },
+    "scripts": {
+      "test": "standard && node my-tests.js"
+    }
+  }
+  ```
+
+2. Check style automatically when you run `npm test`
+
+  ```
+  $ npm test
+  Error: Use JavaScript Standard Style
+    lib/torrent.js:950:11: Expected '===' and instead saw '=='.
+  ```
+
+3. Never give style feedback on a pull request again!
+
+
+
 ### Badge
@@ -236,28 +265,2 @@
 
-### What you might do if you're clever
-
-1. Add it to `package.json`
-
-  ```json
-  {
-    "name": "my-cool-package",
-    "devDependencies": {
-      "standard": "*"
-    },
-    "scripts": {
-      "test": "standard && node my-tests.js"
-    }
-  }
-  ```
-
-2. Check style automatically when you run `npm test`
-
-  ```
-  $ npm test
-  Error: Use JavaScript Standard Style
-    lib/torrent.js:950:11: Expected '===' and instead saw '=='.
-  ```
-
-3. Never give style feedback on a pull request again!
-
 ## FAQ
@@ -308,9 +311,16 @@
 
-Yes! you can install [Max Ogden][max]'s [`standard-format`][standard-format] module
-with `npm install -g standard-format`.
+Yes! You can use `standard --fix` to automatically fix most issues automatically.
 
- `standard-format filename.js` will automatically fix most issues though some,
- like not handling errors in node-style callbacks, must be fixed manually.
+`standard --fix` is built into `standard` (since v8.0.0) for maximum convenience.
+Lots of problems are fixable, but some errors, like not handling errors in
+node-style callbacks, must be fixed manually.
 
-[max]: https://github.com/maxogden
+To save you time, `standard` outputs a message ("Run `standard --fix` to automatically fix some
+problems.") when it detects problems that can be fixed automatically.
+
+Alternatively, if you have an ES5-only codebase, you can try
+[`standard-format`][standard-format] (a separate package), but it likely will not
+be maintained going forward since `standard --fix` works so well, and does not
+require us to maintain two tools with separate rule configurations.
+
 [standard-format]: https://github.com/maxogden/standard-format
@@ -402,4 +412,7 @@
 
-### Can I use a custom JS parser for bleeding-edge ES6 or ES7 support?
+### Can I use a custom JS parser for bleeding-edge ES next support?
 
+Before you use a custom parser, consider whether the added complexity in your
+build process is worth it.
+
 `standard` supports custom JS parsers. To use a custom parser, install it from npm
@@ -419,2 +432,27 @@ (example: `npm install babel-eslint`) and add this to your `package.json`:
 
+### Can I use a JavaScript language variant, like Flow?
+
+Before you use a custom JS language variant, consider whether the added complexity
+in your build process (and effort required to get new contributors up-to-speed) is
+worth it.
+
+`standard` supports ESLint plugins. Use one of these to transform your code into
+valid JavaScript before `standard` sees it. To use a custom parser, install it from
+npm (example: `npm install eslint-plugin-flowtype`) and add this to your
+`package.json`:
+
+```json
+{
+  "standard": {
+    "plugins": [
+      "flowtype"
+    ]
+  }
+}
+```
+
+If you're using `standard` globally (you installed it with `-g`), then you also
+need to install `eslint-plugin-flowtype` globally with
+`npm install eslint-plugin-flowtype -g`.
+
 ### Can you make rule X configurable?
@@ -421,0 +459,0 @@

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

67893

increased by2.45%

Number of lines in readme file

608

increased by6.67%

Dependency changes

• + Addedeslint@3.5.0(transitive)

• + Addedeslint-config-standard@6.0.1(transitive)

• + Addedeslint-config-standard-jsx@3.0.1(transitive)

• + Addedfile-entry-cache@2.0.0(transitive)

• - Removedeslint@3.3.1(transitive)

• - Removedeslint-config-standard@6.0.0-beta.3(transitive)

• - Removedeslint-config-standard-jsx@3.0.0(transitive)

• - Removedfile-entry-cache@1.3.1(transitive)

• Updatedeslint@~3.5.0

• Updatedeslint-config-standard@6.0.1

• Updatedeslint-config-standard-jsx@3.0.1