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
There are situations in which a platform will introduce an import scheme that aren't supported by deno. These schemes should still be publishable to JSR.
The biggest one right now that I'm aware of is cloudflare's cloudflare:* scheme. For example, if you're creating a durable object:
import{DurableObject}from"cloudflare:workers"
Likewise with importing env
import{env}from"cloudflare:workers"
Right now packages that reference these imports can't be published to JSR even though JSR ostensibly supports cloudflare as a suggested deployment target.
There are situations in which a platform will introduce an import scheme that aren't supported by deno. These schemes should still be publishable to JSR.
The biggest one right now that I'm aware of is cloudflare's
cloudflare:*
scheme. For example, if you're creating a durable object:Likewise with importing
env
Right now packages that reference these imports can't be published to JSR even though JSR ostensibly supports cloudflare as a suggested deployment target.
See also #986
The text was updated successfully, but these errors were encountered: