-
Notifications
You must be signed in to change notification settings - Fork 13
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
Sginal should be polyfill to global #10
Comments
I maintain the second two, and no, they do not automatically modify the global - quite intentionally, as that behavior is dangerous. Providing an opt-in mechanism to do so would be great, though, although i hope it would wait until the proposal is at stage 3. |
This is great, this allows me to call Signal in a more good way, what can I do to help we achieve this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This package is named a "*-polyfill", but its behavior is quite different from other typical polyfills. Most polyfills register the target to the global or tagetprototype, such as:
promise-polyfill
object.assign
Array.prototype.map
We should consider whether this approach is appropriate, and whether the current implementation makes it difficult for multiple packages to share the same polyfill.
The text was updated successfully, but these errors were encountered: