wesbos / eslint-config-wesbos

No-Sweat™ Eslint and Prettier Setup - with or without VS Code

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

2.0 Beta Testing

wesbos opened this issue · comments

If anyone wants to test the latest version of this eslint on your project, please do!

There aren't many rule changes, but it's all updated for the latest packages and has support for typescript.

  1. In your project run npx install-peerdeps --dev eslint-config-wesbos@2.0.0-beta.11
  2. In yout .eslintrc file, use { extends: "wesbos" } for JS, or { extends: "wesbos/typescript" } for TS
  3. For JS, you might need a .babelrc file with {} in it, let me know if you do

Let me know if there are any issues. Would like to get this sucker shipped as the current one is clashing with a few libs.

commented

Currently testing beta11
Everything is working fine, had a hard time with prettier so I installed the eslint-prettier extension. .

Edit: not necessary. after some more tinkering, I realized all I had to do was disable the regular prettier extension for ts and tsx like this , to avoid conflicts with eslint.
Formats properly on save and all.

The only issue right now is the no-use-before-define error on import React from 'react'
Fixed it by enabling only the @typescript-eslint version of the rule:

{
    "no-use-before-define": 0,
    "@typescript-eslint/no-use-before-define": 1
}

Got the final answer here

@islami00 thanks, you shouldn't have to install eslint-prettier. Will have a look into it! Will also check those rules

Using Windows 10 and had to have a Babelrc file with empty brackets for js files. let me know if you need anything to debug

Thanks! I'm just looking and I thinkI can avoid that with requireConfigFile. Will try it

https://github.com/babel/babel/tree/main/eslint/babel-eslint-parser#additional-parser-configuration

Yep that did it! No need for the empty babel file now. Thanks again

2.0.0 is out! Let me knwo if you hit anything else!