Linter Flashcards

1
Q

ES Lint for Launch School:

Install es lint at launch school

A

npm install eslint@7.12.1 eslint-cli babel-eslint –save-dev

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

uninstall eslint

A

$ npm uninstall eslint eslint-cli babel-eslint -g

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

ES Lint for Launch School:
use custom settings for eslint

A

When you run ESLint, it looks for this file (and others) in the current directory or the closest parent directory that contains a usable configuration file, but it does not look in your home directory. The easiest way to leverage this search is to put your default .eslintrc.yml file in a directory that contains all of your projects as subdirectories. Alternatively, you can put the file in each project directory and customize it as needed.

In practice, nested configurations are allowed, but can be confusing. Put the .eslintrc.yml file in your top-level projects directory or put it in each individual project directory. Don’t put it in both.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

ES Lint for Launch School:
run eslint in terminal

A

npx eslint hello.js

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

get eslint to work in vscode

A

if everything else is setup, it should automatically work

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

ES Lint for Launch School:

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

ES Lint for Launch School:

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly