CHANGELOG.md

1.3.0

• Add support for multi workspace folder setups. Adding this supoort required a major code change both on the extension and the server side. So if you recognized problems with this version please report them as quick as possbible in the GitHub repository.

  Version 1.3.0 of the ESLint extension requires at least version 1.16 of VS Code.

1.2.11

Fixes:

• (Insiders/1.2.10) "Cannot read property 'then' of undefined

1.2.10

Performance work around code actions and validation. Fixed:

• Slowdown on code assist with eslint enabled

1.2.9

This version was an internal test release which wasn't available in the market place

1.2.8

Fixes:

• Linting is still enabled when viewing git diff.

1.2.7

Fixes:

• Don't lint git diff.

1.2.6

Fixes:

• Do not always run eslint from the project's root directory
• baseDir should be an absolute path

1.2.5

• Validdating a single file (no workspace folder open) will set the working directory to the directory containing the file.
• Added support for working directories. ESLint resolves configuration files relative to a working directory. This new settings allows users to control which working directory is used for which files. Consider the following setups:

client/
  .eslintignore
  .eslintrc.json
  client.js
server/
  .eslintignore
  .eslintrc.json
  server.js

Then using the setting:

  "eslint.workingDirectories": [
    "./client", "./server"
  ]

will validate files inside the server directory with the server directory as the current working directory. Same for files in the client directory. If the setting is omitted the working directory is the workspace folder.

1.2.4

• fixes .eslintignore is completely ignored
• reverted fix for Does not respect nested eslintignore files since it broke the use case of a single global .eslintrc file

1.2.3

• Bug fixes:
  • Does not respect nested eslintignore files
  • eslintrc configuration cascading not being honored
  • autoFixOnSave not working with eslint.run=onSave
  • autoFixOnSave not listed under Settings Options in Readme

1.2.2

• Added configuration options to enable code actions and auto fix on save selectively per language. In release 1.2.1 code actions and auto fix on save very still only available for JavaScript. In 1.2.2 you can now enable this selectively per language. For compatibility it is enabled by default for JavaScript and disabled by default for all other languages. The reason is that I encounter cases for non JavaScript file types where the computed fixes had wrong positions resulting in 'broken' documents. To enable it simply provide an object literal in the validate setting with the properties language and autoFix instead of a simple string. An example is:

"eslint.validate": [ "javascript", "javascriptreact", { "language": "html", "autoFix": true } ]

1.2.1

• Added support to validate file types other than JavaScript. To enable this, you need to do the following:
  • Configure ESLint with an additional plugin to do the actual validation. For example, to validate HTML files install eslint-plugin-html using npm install eslint-plugin-html --save-dev and update the eslint configuration (e.g. .eslintrc.json file) with "plugin": [ "html" ].
  • Add the corresponding language identifier to the eslint.validate setting. Something like "eslint.validate": [ "javascript", "javascriptreact", "html" ]. If the setting is missing, it defaults to ["javascript", "javascriptreact"]

Please note that code actions and auto fix on save is still only available for JavaScript. The reason is that I detected position problems with fixes contributed by plugins resulting in broken source code when applied.

1.1.0

• Supports more than one ESLint module installation in a workspace. This eases working with typical client / server setups where ESLint is installed in a node_modules folder in the server and the client directory.
• Improved error handling if a plugin can't be loaded.
• Added commands to enable and disable ESLint.

1.0.8

• Supports auto fix on save. Needs to be enabled via "eslint.autoFixOnSave": true. Please note that auto fix on save will only happen if the save happened manually or via focus lost. This is consistent with VS Code's format on save behaviour. Auto fix on save requires VS Code version 1.6 or newer.

1.0.7

• Fixed problem with validating package.json when editing .eslintrc.* files.

1.0.5

• Moving to official 2.5.0 language server libraries.

1.0.4

• Bug fixing: eslint is validating package.json files

1.0.3

• Errors in configuration files are only shown in a status message if the file is not open in the editor. Otherwise message are shown in the output channel only.

1.0.2

• Added a status bar item to inform the user about problems with ESLint. A message box only appears if the user attention is required.
• Improved handling of missing corrupted configuration files.
• The ESLint package is now loaded from parent folders as well.
• Added an action to create a .eslintrc.json file.