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
Background: I've been using deno.land/x as an immutable hosting service for modules that can be used both in the browser and in Deno. I think that's sort of what it's designed for - or at least what it will emergently become. That is, as opposed to a hosting service purely for Deno usage.
Problem: A decent portion of modules on deno.land/x are understandably .ts modules. This means that if I want to import them into the browser, I need to transpile them, and then upload them somewhere (probably deno.land/x). It would be really, really cool if there were a way to get the deno.land/x server to do that. Something like one of these, perhaps:
Background: I've been using deno.land/x as an immutable hosting service for modules that can be used both in the browser and in Deno. I think that's sort of what it's designed for - or at least what it will emergently become. That is, as opposed to a hosting service purely for Deno usage.
Problem: A decent portion of modules on deno.land/x are understandably
.ts
modules. This means that if I want to import them into the browser, I need to transpile them, and then upload them somewhere (probably deno.land/x). It would be really, really cool if there were a way to get the deno.land/x server to do that. Something like one of these, perhaps:The deno.land/x server would obviously save/cache the result such that this feature would add very little extra computation burden to the service.
Is a feature like this feasible?
The text was updated successfully, but these errors were encountered: