Skip to content
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

"Cannot find module 'eslint-interactive' or its corresponding type declarations" in fixable-maker-script and filter-script #255

Open
mizdra opened this issue Feb 4, 2023 · 2 comments
Labels
Type: Bug Bug or Bug fixes

Comments

@mizdra
Copy link
Owner

mizdra commented Feb 4, 2023

Opening fixable-maker-script and filter-script in VSCode displays a tsc error.

image

@mizdra mizdra added the Type: Bug Bug or Bug fixes label Feb 4, 2023
@mizdra
Copy link
Owner Author

mizdra commented Feb 4, 2023

Other type definition files seem to be loaded successfully.

image

image

~/Library/Caches/typescript/xxx/node_modules is the directory where type definitions fetched by VSCode's Automatic Type Acquisition are stored.

According to the description of the relevant options in VSCode, Automatic Type Acquisition only fetches type definitions in the @types scope.

Disables automatic type acquisition. Automatic type acquisition fetches @types packages from npm to improve IntelliSense for external libraries.

from: https://github.com/microsoft/vscode/blob/91fccee240d37132a12cc0818d37f6064a93c80f/extensions/typescript-language-features/package.nls.json#L12

I think the reason why eslint-interactive type definitions are not loaded is because @types/eslint-interactive is not published.

@mizdra
Copy link
Owner Author

mizdra commented Feb 24, 2023

Ideas: Embed only those eslint-interactive type definitions that are needed inline in the file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Bug or Bug fixes
Projects
None yet
Development

No branches or pull requests

1 participant