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
If we can shorten this down to a single import, the whole thing could be:
import{setupKolay}from'kolay/setup';// a virtual module// ...constmanifest=awaitsetupKolay({resolve: {'my-library': awaitimport('my-library'),'something-else': awaitimport('something-else'),},});
which, I think, makes more sense, and kolay/setup is easy to provide type definitions for.
But, so far, a virtual module cannot import another virtual module, because plugins' resolve hooks are only used when resolving from the consuming app and a virtual module is kind of in a void of its own.
The text was updated successfully, but these errors were encountered:
Right now, folks have to do this in their apps:
This isn't great because:
previously issues that are now non issues
If we can shorten this down to a single import, the whole thing could be:
which, I think, makes more sense, and
kolay/setup
is easy to provide type definitions for.But, so far, a virtual module cannot import another virtual module, because plugins' resolve hooks are only used when resolving from the consuming app and a virtual module is kind of in a void of its own.
The text was updated successfully, but these errors were encountered: