-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[browser] detect and assert engine features #88846
Conversation
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -26,7 +26,20 @@ let mono_wasm_web_socket_close_warning = false; | |||
const ws_send_buffer_blocking_threshold = 65536; | |||
const emptyBuffer = new Uint8Array(); | |||
|
|||
function verifyEnvironment() { | |||
if (ENVIRONMENT_IS_SHELL) { |
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.
Shoud we move it after the typeof globalThis.WebSocket !== "function"
condition?
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.
for some random polyfill ? I don't think so.
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.
Yes, for some polyfill, or if it happens to be added... What is the reason to be that restrictive?
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.
It has complex dynamic behavior and even the nodeJS polyfill doen't work well in all use-cases. I'm just loud and clear this is not supported.
This will fail fast during startup, if we don't have necessary JS APIs.
Contributes to #84574
Contributes to #76961