# eslint-config-cvviz

> Default ESLint config for CVViZ Apps

Latest version **1.0.4** (published 2022-07-12) · MIT license · 0 weekly downloads

## Install

```sh
npm install eslint-config-cvviz
pnpm add eslint-config-cvviz
yarn add eslint-config-cvviz
bun add eslint-config-cvviz
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.4 |
| Published | 2022-07-12 |
| First published | 2022-07-11 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 17.2 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Satyawan Jagankar |
| Maintainers | satyawan-jagankar |

## Links

- npm: https://www.npmjs.com/package/eslint-config-cvviz
- Repository: git@github.com:cvviz/eslint-config-cvviz
- npm.io page: https://npm.io/package/eslint-config-cvviz

## Recent versions

- 1.0.4 (latest) — 2022-07-12
- 1.0.3 — 2022-07-12
- 1.0.2 — 2022-07-11
- 1.0.1 — 2022-07-11
- 1.0.0 — 2022-07-11

## README

# eslint-config-cvviz
Default ESLint config for CVViZ Apps

## What it does
* Lints JavaScript based on the latest standards
* Fixes issues and formatting errors with Prettier
* Lints + Fixes inside of html script tags
* Lints + Fixes React via eslint-config-airbnb
* You can see all the [rules here](https://github.com/cvviz/eslint-config-cvviz/blob/main/.eslintrc.js)

## Installation

## Local / Per Project Install


1. Install peer dependencies needed by the config:

```
npx install-peerdeps --dev eslint-config-cvviz
```

2. Create a `.eslintrc` file in the root of your project's directory (it should live where package.json does). Your `.eslintrc` file should look like this:

```json
{
  "extends": [ "cvviz" ]
}
```

For TypeScript projects, use `cvviz/typescript`.

```json
{
  "extends": [ "cvviz/typescript" ]
}
```

TypeScript users will also need a `tsconfig.json` file in their project. An empty object (`{}`) will do if this is a new project.


Tip: You can alternatively put this object in your `package.json` under the property `"eslintConfig":`. This makes one less file in your project.

3. You can add two scripts to your package.json to lint and/or fix:

```json
"scripts": {
  "lint": "eslint .",
  "lint:fix": "eslint . --fix"
},
```

3. Now you can manually lint your code by running `npm run lint` and fix all fixable issues with `npm run lint:fix`. You probably want your editor to do this though.

## Settings

If you'd like to overwrite eslint or prettier settings, you can add the rules in your `.eslintrc` file. The [ESLint rules](https://eslint.org/docs/rules/) go directly under `"rules"` while [prettier options](https://prettier.io/docs/en/options.html) go under `"prettier/prettier"`. Note that prettier rules overwrite anything in my config (trailing comma, and single quote), so you'll need to include those as well.

```js
{
  "extends": [
    "cvviz"
  ],
  "rules": {
    "no-console": 2,
    "prettier/prettier": [
      "error",
      {
        "trailingComma": "es5",
        "singleQuote": true,
        "printWidth": 120,
        "tabWidth": 8,
      }
    ]
  }
}
```

## With VS Code

You should read this entire thing. Serious!

Once you have done one, or both, of the above installs. You probably want your editor to lint and fix for you. Here are the instructions for VS Code:

1. Install the [ESLint package](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint)
2. Now we need to setup some VS Code settings via `Code/File` → `Preferences` → `Settings`. It's easier to enter these settings while editing the `settings.json` file, so click the Open (Open Settings) icon in the top right corner:
  ```js
  // These are all my auto-save configs
  "editor.formatOnSave": true,
  // turn it off for JS and JSX, we will do this via eslint
  "[javascript]": {
    "editor.formatOnSave": false
  },
  "[javascriptreact]": {
    "editor.formatOnSave": false
  },
  // show eslint icon at bottom toolbar
  "eslint.alwaysShowStatus": true,
  // tell the ESLint plugin to run on save
  "editor.codeActionsOnSave": {
    "source.fixAll": true
  }
  ```

After attempting to lint your file for the first time, you may need to click on 'ESLint' in the bottom right and select 'Allow Everywhere' in the alert window. 

Finally you'll usually need to restart VS code. They say you don't need to, but it's never worked for me until I restart.
## With Typescript

Same instructions as above, just make sure you extend `cvviz/typescript` instead of just `cvviz`.

## With Yarn

It should just work, but if they aren't showing up in your package.json, try `npx install-peerdeps --dev eslint-config-cvviz -Y`

## Issues with ESLint not formatting code

If you experience issues with ESLint not formatting the code or you receive a `Parsing error: Cannot find module '@babel/preset-react` error message then you need to check that you opened the folder where you installed and configured ESLint directly in VS Code. The correct folder to open will be the one where you installed the `eslint-config-cvviz` npm package and where you created the `.eslintrc` file.

Opening a parent folder or child folder in your code editor will cause ESLint to fail in finding the ESLint npm packages and the formatting won't work.

```sh
your-username
  |
  projects
    |
    beginner-javascript # <- Open this folder directly in your code editor
      .eslintrc
      package.json
      node_modules/
      exercises/
      playground/
```

---
_Source: https://npm.io/package/eslint-config-cvviz · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._