93c10dfa6b
If something throws as a result of `flushSync`, and there's remaining work left in the queue, React should keep working until all the work is complete. If multiple errors are thrown, React will combine them into an AggregateError object and throw that. In environments where AggregateError is not available, React will rethrow in an async task. (All the evergreen runtimes support AggregateError.) The scenario where this happens is relatively rare, because `flushSync` will only throw if there's no error boundary to capture the error. |
||
|---|---|---|
| .. | ||
| plugins | ||
| shims | ||
| validate | ||
| wrappers | ||
| build-all-release-channels.js | ||
| build.js | ||
| bundles.js | ||
| forks.js | ||
| generate-inline-fizz-runtime.js | ||
| modules.js | ||
| packaging.js | ||
| stats.js | ||
| sync.js | ||
| utils.js | ||
| wrappers.js | ||