Debug TypeScript ESLint paths resolution

[osdiab]

Hi, I normally use VSCode and considering a jump to Zed, but out of box it is highlighting an import to a path configured via the TypeScript paths property as a problem because it is not resolvable according to ESLint (but not according to TypeScript).

How would one go about debugging this Zed behavior? Perhaps the LSP for ESLint isn't actually catching my .eslintrc.js? Thanks!

[SomeoneToIgnore]

Hi, the best way so far would be

• LSP logs (debug: open language server logs in the action panel)
• Zed logs for the large calamities like LSP server did not start at all

Another way would be to add more debug logs (and, maybe, even turn those into a PR later) and run a debug version of Zed to see what's happening.
#3457 was the last attempt to adjust eslint diagnostics and could serve as a reference where to log things.

[osdiab]

Looks like the LSP logs don't have much info: ``` ESLint library loaded from: ***@***.*** /node_modules/eslint/lib/api.js stderr: Warning: React version was set to "detect" in eslint-plugin-react settings, but the "react" package is not installed. Assuming latest React version for glinting. ``` Not sure where it's getting the ESLint config from or anything. So yeah I guess the LSP logs are just not very thorough yet. I'll probably come back to Zed once it's had a bit more time to mature, thanks! Omar

…

On Mon, Jan 29, 2024 at 8:52 PM, Kirill Bulatov ***@***.***> wrote: Hi, the best way so far would be - LSP logs (debug: open language server logs in the action panel) - Zed logs for the large calamities like LSP server did not start at all Another way would be to add more debug logs (and, maybe, even turn those into a PR later) and run a debug version of Zed to see what's happening. #3457 <#3457> was the last attempt to adjust eslint diagnostics and could serve as a reference where to log things. — Reply to this email directly, view it on GitHub <#6977 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAONU3UFXEXMOTOHYGFQGL3YQ6EQRAVCNFSM6AAAAABCPDS35KVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DEOBRGA4TI> . You are receiving this because you authored the thread.Message ID: ***@***.***>