You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a .eslintrc.cjs config file for eslint to support the next.js plugin. Eslint works as expected when I run npm run lint, but when I use zed.dev integrated with typescript-language-server, I don't see these diagnostics.
I am specifically interested in the react-hooks diagnostics.
If you suspect that this is a zed.dev problem rather than a typescript-language-server problem, please let me know how I can validate that this problem is caused by typescript-language-server
The text was updated successfully, but these errors were encountered:
This server has nothing to do with eslint. It doesn't integrate with it
There might exist typescript plugins that run eslint but it's out of scope of this server if Zed is using those. I would anyway recommend running a separate LSP server for eslint.
I got the idea that eslint was integrated from this issue. #159
Seeing your response, I see the confusion around internal use of eslint vs integration of eslint. Sorry for the confusion. Thanks for the quick response :)
I have a .eslintrc.cjs config file for eslint to support the next.js plugin. Eslint works as expected when I run
npm run lint
, but when I use zed.dev integrated with typescript-language-server, I don't see these diagnostics.I am specifically interested in the react-hooks diagnostics.
If you suspect that this is a zed.dev problem rather than a typescript-language-server problem, please let me know how I can validate that this problem is caused by typescript-language-server
The text was updated successfully, but these errors were encountered: