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
In a project I'm working on, I dynamically load various modules using the async import() call, the list of modules is loaded from a .ts config file, but it's unfortunately just an array of literal strings.
It would be really helpful if I could give it a type of ModuleSpecifier[] for example, and then have the same editor experience for these values as you'd get for the parameter of an import(...) call.
A step beyond this, it would also be useful for tooling to be able to optionally include any ModuleSpecifier declared literals in the module graph.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In a project I'm working on, I dynamically load various modules using the async
import()
call, the list of modules is loaded from a .ts config file, but it's unfortunately just an array of literal strings.It would be really helpful if I could give it a type of
ModuleSpecifier[]
for example, and then have the same editor experience for these values as you'd get for the parameter of animport(...)
call.A step beyond this, it would also be useful for tooling to be able to optionally include any
ModuleSpecifier
declared literals in the module graph.Beta Was this translation helpful? Give feedback.
All reactions