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? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add a TypeScript declaration file.
import promise from 'eslint-plugin-promise'
eslint-plugin-promise
Expected behavior: [What you expect to happen]
Get no errors.
Actual behavior: [What actually happens]
Get errors in VSC about TS types
The text was updated successfully, but these errors were encountered:
Should we go all in with checkJs: true, basically going full JavaScript+JSDoc-as-TypeScript?
checkJs: true
Sorry, something went wrong.
Real life example from neostandard: https://github.com/neostandard/neostandard/blob/08ae5469c71def357f0202fed2be9b83f62efc5a/lib/configs/base.js#L5
I have a PR for that in another project, so I’m +1 on it
Will probably wait on #484 to begin any work here, as don't want the tooling to have to be outdated to be supported...
Agree @brettz9 👍 And I think @scagood is also interested in this topic :)
voxpelli
Successfully merging a pull request may close this issue.
Description
Add a TypeScript declaration file.
Steps to Reproduce
import promise from 'eslint-plugin-promise'
eslint-plugin-promise
in VSCExpected behavior: [What you expect to happen]
Get no errors.
Actual behavior: [What actually happens]
Get errors in VSC about TS types
The text was updated successfully, but these errors were encountered: