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

Draft: Improve Deno compatibility (v2) #3428

Closed
wants to merge 6 commits into from
Closed

Conversation

rth
Copy link
Member

@rth rth commented Jan 5, 2023

Similar to #3421 bit with more code reuse from the Node.js implementation.

Not ready for a review yet.

@rth rth mentioned this pull request Jan 5, 2023
3 tasks
);
(globalThis as any).XMLHttpRequest = XHRModule.default;

let denoStdlib = "https://deno.land/[email protected]/";
Copy link
Member Author

@rth rth Jan 5, 2023

Choose a reason for hiding this comment

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

@josephrocca just curious, in your experience, is it OK to hardcode the stdlib version used this way in libraries in Deno, or is there a better packaging solution?

@@ -8,10 +8,14 @@ export const IN_NODE =
typeof process.browser ===
"undefined"; /* This last condition checks if we run the browser shim of process */

export const IN_DENO = "Deno" in window;
Copy link
Member

Choose a reason for hiding this comment

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

Some people have requested a loadPyodide "runtime" argument that can override the automatic feature detection. It might be a bit annoying to set up though.

@rth rth mentioned this pull request Apr 19, 2023
6 tasks
@rth
Copy link
Member Author

rth commented May 12, 2023

Closing in favor of #3420 (comment)

@rth rth closed this May 12, 2023
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