-
-
Notifications
You must be signed in to change notification settings - Fork 888
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
Conversation
); | ||
(globalThis as any).XMLHttpRequest = XHRModule.default; | ||
|
||
let denoStdlib = "https://deno.land/[email protected]/"; |
There was a problem hiding this comment.
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; |
There was a problem hiding this comment.
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.
Closing in favor of #3420 (comment) |
Similar to #3421 bit with more code reuse from the Node.js implementation.
Not ready for a review yet.