Sebastian Markbåge
Sebastian Markbåge
Technically either this or assert syntax could be repurposed for this syntax, but they’re not quite the same concept. It’s more of a hack. These other has some interesting consequences...
@lucacasonato I see. I buy that. Import reflections should be applied late, but import assertions would be applied early when combined with asset references. The important thing is that then...
Which part? The main things asset references provide is just formalizing the `import('specifier')` and `new URL('specifier', import.meta.url)` patterns into a standard syntax and make it nicer by avoiding intermediates. However,...
Yea, the main thing is that `import(...)` is async. Not even a micro-task. Even if you preload into the HTTP cache, you need a macro-task to pull it up. In...
What I really want is `preload('specifier').then(module => execute(module).thisIsSynchronouslyAvailable);`
Preloading locally is just one. Another use case is getting a reference on the server using server-side JS and then passing that reference along to trace where it's used and...
`unstable_batchedUpdates` is a way to deprioritize an update by delaying it. The default priority is even more delayed and more batched than `unstable_batchedUpdates`. So `unstable_batchedUpdates` is a noop in React...
It's because useSyncExternalStore always has to be flushed at the highest priority where as other updates can be delayed. It can't be delayed because of the "Sync" part which is...
The interesting thing about these things is whether it's observable behavior or a perf consideration. If the useEffects observing the rendering or painting by the browser, while still being implemented...