Jason Miller

Just going to clarify for folks finding this issue - Greenlet does re-use the worker thread for all calls, but only if you hoist the greenlet() definition so it's being...

@ImedAdel that works, yup! There's also [workerize](https://GitHub.com/developit/workerize), which is basically like Greenlet but with support for "exporting" multiple methods from the worker.

Oh I didn't mean the loader - there is a non-loader version of workerize that uses the same internals as Greenlet, works at runtime.

You shouldn't be running prettier or eslint on generated output files. I'm not sure how the vue-cli prettier plugin you're using works, but you'll want to find a way to...

What does your worker code look like? I can't think of a reason why Prettier would complain about core-js require() statements other than them simply being present in the worker...

FWIW this appears to be a specific issue with `@vue/cli`.

Hi @epavan - you can't pass Promises to greenlet, because the code that generates the work those promises represent would still just be running on the main thread. It's likely...

Absolutely! We added it to greenlet in only a few bytes, the same solution should work reasonably well here. It would only auto-detect transferables passed directly as arguments, not within...

They are not currently supported.

I'm not against that, but it would make statically analyzing the exports mostly impossible. One direction I'd thought of going for a 2.0 (that happens to unify workerize and workerize-loader)...