Janus Reith

@zenweasel This is still available and for example in use here: https://github.com/reactioncommerce/api-plugin-sitemap-generator/blob/88c9e71d62c096ab182bf7a101ff4bae315d7e44/src/startup.js#L19 However, similar to the considerations in https://github.com/reactioncommerce/reaction/issues/6279 defining these routes during runtime, while very flexible, is not optimal...

I'm wondering, since the node API works in ESM mode, and all of the api modules are distributed as ESM too, could the API modules list `peerdependencies` instead, and could...

Hi @bayareacoder, first of all, I agree on all three points you raised, especially regarding 3 I think some work could be done to generalize and simplify CRUD Operations. >...

@bayareacoder Awesome! I had a similar idea in mind for some time, but never actually implemented it. Would love to see what you came up with sometime if that is...

>This one is critical because it will not throw an error but just give you the old document Wow, changes like this are hard to understand.

I wonder if we could just provide an easy migration path here to keep compatibility. Especially regarding that case of `returnOriginal`, since calls don't go right to the mongodb package...

> I use napi-rs to run compute heavy tasks off the main thread and I'm not sure how well that translates to the browser. While the output should be able...

Thanks for the quick response, and thanks for looking into it! For my specific usecase HTTP1 would probably be fine, I‘m expecting larger bottlenecks on other levels. Let me know...

The @swc/jest repo, which exists specifically for jest, even mentions using Jest with ESM, however that simply won't work once I actually want to type-check my code (Which I would...

This seems to be related: https://github.com/swc-project/swc/issues/3043