Introducing Multi-threading

[vezaynk]

Introducing multi-threading to off-load React SSR to work threads.

• Multi-threaded rendering available in production mode only.
• Worker pooling is setup using resource-pooler
• Transform All hooks are no longer a function, but a path to import a function to use

I will leave comments on the diff discussing every important part for easier reviewing

Todos:

• make nonces work
• unit tests for hooks

[vezaynk]

I'm updating most dev dependencies to make the linter accept satisfies.

[vezaynk]

@airhorns wds needs to have a version bump to @swc/core applied. satisfies doesn't build without it.

[airhorns]

I think this catch is going to catch any errors importing the actual target file, like syntax errors or runtime issues. Could we drive the decision to use ts-node or not with an environment variable or some other explicit instruction?

[vezaynk]

I think magic flags should be avoided imo, especially given that it only matters in development of this package itself.

.ts files will never appear in the built package, which will make this always throw when distributed, and always load the js file instead.

It's safe in that respect.

I can do it based on the existence of a .ts file instead. Would that be better?

[vezaynk]

@airhorns Actually this can be handled really nicely via vite, but I can't do that right now because the test app doesn't use vite. It could be a small project for later if you like.