Skip to content

Add the ability to ignore schemes #1034

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

Open
zephraph opened this issue Apr 15, 2025 · 1 comment · May be fixed by #1035
Open

Add the ability to ignore schemes #1034

zephraph opened this issue Apr 15, 2025 · 1 comment · May be fixed by #1035

Comments

@zephraph
Copy link

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.


See also #986

@github-project-automation github-project-automation bot moved this to Needs Triage in JSR Apr 15, 2025
@crowlKats crowlKats moved this from Needs Triage to Needs Plan in JSR Apr 15, 2025
@crowlKats
Copy link
Collaborator

We are more inclined in adding specific schemes currently, so we will add support for cloudflare: specifiers

@crowlKats crowlKats linked a pull request Apr 15, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs Plan
Development

Successfully merging a pull request may close this issue.

2 participants