-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.0 Beta Testing #97
Comments
Currently testing beta11 Edit: not necessary. after some more tinkering, I realized all I had to do was disable the regular prettier extension for The only issue right now is the {
"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 |
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! |
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.
npx install-peerdeps --dev [email protected]
.eslintrc
file, use{ extends: "wesbos" }
for JS, or{ extends: "wesbos/typescript" }
for TS.babelrc
file with{}
in it, let me know if you doLet me know if there are any issues. Would like to get this sucker shipped as the current one is clashing with a few libs.
The text was updated successfully, but these errors were encountered: