Andrea Giammarchi

> Mutation observer: potentially reflect that there was a move It's already easy to fail behind MutationRecords order (added VS removed, which to check first? I check removed first and...

As a developer, I'd like to answer with my expectations about his PR. Since we've slightly discussed this already and we seem to be on the same page, I hope...

@bmeck so is `import` ... it's part of the specifications. I thought the point here is to clearly differentiate as explicit flag intent between CJS and ESM, and I've answered...

> This pull request continues to use import() within CJS as a means of loading ESM. good, I'm OK with that, 'cause I've never used/needed `import(...)` in CJS. Please find...

the test works though ... I am not sure when/where/how you are having issues ... can you share a minimal broken example code instead of your fix? thanks!

Shared Workers can't have access to the `window` object ... would that be OK? I am thinking about a `coincident/shared/main` and `coincident/shared/worker` exports 🤔

@nickchomey what I am asking is: do you expect the ability to deal with the `window` main thread object in there? 'cause AFAIK *SharedWorker* can be used cross tabs too,...

so ... `coincident/main` and `coincident/worker` allow workers to invoke functions from main in a synchronous way and without blocking, while the main thread can invoke workers functions asynchronously (hence still...

After refining this module lately to avoid every single possible detail that could interfere with each other when running in a multiple workers or servers scenario (no more shared HEAP,...

P.S. the more I think about this request, the more I feel like it's just an indirection of what I do already with **server** export ... server in that case...