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
Now in my code where I use the import I always have to add the types comment to it in order to have correct IDE complition and properly understand what method and what arguments and what types it takes
// @deno-types="@types/yargs"
import yargs from 'yargs'
My proposal is, may be to support something like that in the imports statements:
At least this)
ideally Deno should resolve the type definitions as Node js does, an not have to do all these workasounds
But at least something rather than adding comments in the code
The text was updated successfully, but these errors were encountered:
Let's say I install a package from npm by adding this to my deno.json imports (Any package, just as example)
Now in my code where I use the import I always have to add the types comment to it in order to have correct IDE complition and properly understand what method and what arguments and what types it takes
My proposal is, may be to support something like that in the imports statements:
At least this)
ideally Deno should resolve the type definitions as Node js does, an not have to do all these workasounds
But at least something rather than adding comments in the code
The text was updated successfully, but these errors were encountered: