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

Feature: New process polyfill approach #8187

Closed
hwillson opened this issue May 10, 2021 · 1 comment
Closed

Feature: New process polyfill approach #8187

hwillson opened this issue May 10, 2021 · 1 comment

Comments

@hwillson
Copy link
Member

This issue tracks the introduction of a new process polyfill approach.

Relates to:

@benjamn
Copy link
Member

benjamn commented Jun 16, 2021

Fixed by #8347, though there may still be opportunities to improve the way we throw invariant and InvariantError exceptions in production, perhaps by dynamically fetching a module with all the error strings in it, or something along those lines. Dynamic import() might not be universally supported, but it only has to work with most applications/bundlers to be an improvement over opaque Invariant Violation 23 errors (improved by #6665, but still annoying).

@benjamn benjamn closed this as completed Jun 16, 2021
@benjamn benjamn moved this from In progress to Done in Release 3.4 Jun 16, 2021
@hwillson hwillson removed this from the MM-2021-06 milestone Jul 29, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Development

No branches or pull requests

2 participants