-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Support non-code AMD modules #279
Comments
I ran into this issue before and worked around it by creating an ambient declaration for the module.
Now, I can load the module like this:
|
This is fixed in 1.5, you can specify a |
We have talked about allowing type annotation on module imports. something like: import * as n: any from "mod"; |
@mhegazy I would very much like that. Not only to type html imports as strings, but also for types that are "map"'d, so you don't have to write a definition to map the name to the actual type. |
@RichiCoder1, i am interested to know what you mean by "mapped". Would that be something covered by mapping paths for module? can you take a look at #2338, and see if this fits your scenario? |
is a type parameter on the amd-dependency possible? e.g. typescript 1.4
typescript 1.5
typescript 1.x ?
|
@lukeapage it is just a proposal at this point. it has not been implemented. if and when it is added, i do not think it will be in an |
Should be addressed by #6615 |
Original issue on CodePlex: https://typescript.codeplex.com/workitem/1046
Problem
Need to
require
text, CSS, and other non-code things.Partial workaround
Use the
/// <amd-dependency path="x" />
tag.Why workaround is not good enough
Have to type the module name twice.
The text was updated successfully, but these errors were encountered: