Skip to content

support deno resolution as a fallback in require #29811

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nathanwhit
Copy link
Member

No description provided.

@nathanwhit nathanwhit force-pushed the require-everything branch from d6c369b to 0bfecca Compare June 18, 2025 21:20
TNpmPackageFolderResolver,
TSys,
>>();
let graph_container = state.borrow::<crate::GraphContainerWrapper>();
Copy link
Member

@dsherret dsherret Jun 18, 2025

Choose a reason for hiding this comment

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

It's probably too much to expose all the way down here and also it creates a dependency on deno_graph for Deploy as well as deno compile. Probably we should have a trait that gets passed down here and then the CLI and deno compile can implement this separately (maybe just put it as a method on NodeRequireLoader)

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.

2 participants