Skip to content
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

fix: hook into deno.json for deno dependencies #290

Merged
merged 3 commits into from
Apr 5, 2023
Merged

fix: hook into deno.json for deno dependencies #290

merged 3 commits into from
Apr 5, 2023

Conversation

Bubblyworld
Copy link
Contributor

Fixes #289, or at least a first pass of a fix. This does the simplest thing for
now, which is to use the top-level imports for resolving a deno package's
secondary dependencies. This gets the denoland:fresh/runtime.ts example
working, for instance.

src/providers/deno.ts Outdated Show resolved Hide resolved
// be to have each provider declare what registries it supports, and
// construct a providers mapping at init when we detect default provider:
if (opts.defaultProvider.includes("deno"))
this.providers["npm:"] = "jspm.io";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps only override this.providers['npm:'] if it doesn't already exist? But yes, this seems fine for now.

Copy link
Member

@guybedford guybedford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Bubblyworld Bubblyworld merged commit 657cd91 into main Apr 5, 2023
@Bubblyworld Bubblyworld deleted the guy-289 branch April 5, 2023 07:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Hook into deno.json when resolving dependencies for denoland packages.
2 participants