We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Opening fixable-maker-script and filter-script in VSCode displays a tsc error.
The text was updated successfully, but these errors were encountered:
Other type definition files seem to be loaded successfully.
~/Library/Caches/typescript/xxx/node_modules is the directory where type definitions fetched by VSCode's Automatic Type Acquisition are stored.
~/Library/Caches/typescript/xxx/node_modules
According to the description of the relevant options in VSCode, Automatic Type Acquisition only fetches type definitions in the @types scope.
@types
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
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.
Sorry, something went wrong.
Ideas: Embed only those eslint-interactive type definitions that are needed inline in the file.
eslint-interactive
No branches or pull requests
Opening fixable-maker-script and filter-script in VSCode displays a tsc error.
The text was updated successfully, but these errors were encountered: