-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
allow type 'unsafe' way to doing es6 style imports #6371
Comments
I think the solutions and discussion in #2709 covers this scenario. |
Though, the way you should be fixing this is by declaring the module itself: declare module "randomLib" {
export let A: any;
} |
this is not feasible for large projects. now for every library we want to use we have to manually create the kinda defeats the whole 'superset of JavaScript' message. On Tuesday, January 5, 2016, Daniel Rosenwasser notifications@github.com
Prashant |
I agree, this is extremely frustrating for people who are migrating. Tangentially, what libraries are you trying to use that don't have typings? Just curious. |
This came up during the migrate-a-thon as well. The long tail of libraries is surprisingly long. |
I don't think #2709 wouldn't be the best fix for this issue. When you've got typings for a library later on, you would need to remove declare module "foo";
declare module "bar"; After declaring these modules in a |
+1 to @ivogabe |
closing in favor of #6615 |
Currently if have an import of a library which doesnt have any type definition, like this:
Typescript will mark an error saying it cant find
randomLib
anywhere.We need some way of telling typescript to suppress the error for this particular import.
The text was updated successfully, but these errors were encountered: