You can choose how you want to apply the worker bit, I just like using a querystring because it's super unintrusive.pic.twitter.com/NCvYYf2tCC
Prikaži ovu nit
Just published comlink-loader 2.0.
Add a querystring to imports and they run in a Worker.
Simple and @typescript works by default.
http://github.com/GoogleChromeLabs/comlink-loader/releases/tag/2.0.0 …pic.twitter.com/tsUzWDS3Wz
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I think the TS types are still misleading if your exported (worker) functions are not promise-returning, since they will be when run in the worker. We have something like this and had to do things differently so we could map the exported function types to always be promise-ey :/
-
It's true there's a delta. For my own purposes and as a general recommendation, I just make all of my exports async. That way the interface is unchanged whether it's used in a worker or on the same thread.
Kraj razgovora
Novi razgovor -
-
-
does this also work with classes?
-
As it uses comlink under the hood, I'm pretty sure the answer is yes :)
Kraj razgovora
Novi razgovor -
-
-
Nice work! I'm presently using comlink with worker-plugin. The advantage there is that I'm not writing webpack specific code which I guess I would be if I were using comlink-loader. Do you have a rule of thumb around which is preferable and when?
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Reminds me of the good ol' days of RequireJS
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.