ESlint extension should be used without npm modules about vscode-eslint HOT 10 CLOSED

@OshotOkill

You can install eslint globally using 'npm install -g eslint' and vscode-eslint will pick it up.

Also eslint supports a cascading lookup so you only have to define a .eslintrc.json file once in a parent folder and it will be picked up.

Is this sufficient for you?

from vscode-eslint.

@egamma Thanks.

from vscode-eslint.

I've had some trouble getting the extension to work with a globally installed eslint. Restarting VS Code a few times seemed to do the trick.

I agree that having to install the NPM package yourself seems a little weak sauce to me, even if it is installed globally. It would be nice if I could install the extension and just see things start working.

from vscode-eslint.

Why Linting Javascript Out-of-the-box when you install ESlint extension is not possible? Thats not convenient for new users and for users who can't use npm for security reason.

from vscode-eslint.

Agreed that it seems like an unnecessary requirement to have users also install eslint globally on their own. I've never had an editor extension that didn't install itself with all dependencies included.

from vscode-eslint.

I would much rather ESLint be bundled with the extension than having to install it globally. I believe the VSCode TSLint extension already does this. https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-typescript-tslint-plugin

from vscode-eslint.

I am still not a fan of this since it forces the ESLint extension to do a catchup game with the eslint npm module. I would rather add an action that installs it.

from vscode-eslint.

I'm teaching web design and JavaScript. From my perspective, it would be great if students starting out with JavaScript could get the hints from ESLint without having to install and invoke NodeJS.

from vscode-eslint.

A PR to contribute an action / command is still very welcome.

from vscode-eslint.

I am closing the issue. Instead of adding this to the eslint extension a better approach would be to have an extension that prereqs this one and guides the user through a possible ESLint setup. This leave this extension somehow light weight and clean.

from vscode-eslint.