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 am unable to "Goto Type Definition..." or "Goto Definition..." on eslint-plugin-perfectionist. It works for @eslint/js, globals, and typescript-eslint in eslint.config.mjs.
I originally found this issue in a new Angular project and opened this ticket with the plugin developers. They have been very helpful in looking into this issue, but believe it is outside of their code. I created the above brand new repo to try and replicate the bug. But I was not able to get the same error message. However the code discovery actions are not working so it feel like there is something here to diagnose. But I am uncertain how to proceed.
The text was updated successfully, but these errors were encountered:
The error message I get with the angular project is of the form:
Cannot find module * or its corresponding type declarations. typescript(2307)
There are types at *, but this result could not be resolved under your current 'moduleResolution' setting. Consider updating to 'node16', 'nodenext', or 'bundler'.
I do not see this error with the minimal reproduction, but I assume it is related.
I am unable to "Goto Type Definition..." or "Goto Definition..." on
eslint-plugin-perfectionist
. It works for@eslint/js
,globals
, andtypescript-eslint
ineslint.config.mjs
.Minimal reproduction repo: https://github.com/rgant/tmp-eslint-perfectionist-test
Trouble Shoot Server Output
Troubleshooting: LSP-typescript
Version
Server Test Run
Server Configuration
/Users/rgant/.nvm/versions/node/v22.12.0/bin/node "/Users/rgant/Library/Caches/Sublime Text 3/Package Storage/LSP-typescript/22.12.0/typescript-language-server/node_modules/typescript-language-server/lib/cli.mjs" --stdio
Active view
Project / Workspace
[ "/Users/rgant/Programming/tmp-eslint-perfectionist-test" ]
LSP configuration
System PATH
I originally found this issue in a new Angular project and opened this ticket with the plugin developers. They have been very helpful in looking into this issue, but believe it is outside of their code. I created the above brand new repo to try and replicate the bug. But I was not able to get the same error message. However the code discovery actions are not working so it feel like there is something here to diagnose. But I am uncertain how to proceed.
The text was updated successfully, but these errors were encountered: