Pooya Parsa

(docs updated)

Ah thanks yes i was looking for that.

Investigating such issues with higher-order metaframeworks is time-consuming. I appreciate it if you could make a minimal reproduction (with mlly utils only). closing in the meantime.

Thanks for the reproduction. I think same as https://github.com/unjs/jiti/issues/204#issuecomment-1894357666 for jiti, for mlly we can leverage `import.meta.resolve` (that yarn pnp provides) if available but only have to make sure result...

I appreciate your work on this. With introduction of `jiti/register`, i think we can instead suggest people to directly use Node.js ESM loader for better debugging.

Nice progress. I was not sure when your work would be ready to review if it is i can happily update to merge and iterate.

This isn't a bug but expected behavior. We should improve documentation to clarify it. We could also introduce a new option like `peer.publish(topic, message, { self: true })` to enable...

Native behavior of Bun pub/sub publish is to publish to all excluding self ([docs](https://bun.com/docs/api/websockets#pub-sub)), and I think the same for some others, so if we want to introduce `self: true`,...

Hi @MielPoule. Seems a nice idea. We (with @Atinux) was thinking about something similar for `fluid` behavior. It seems to me a more generic shortcut with `sizes="xvw"` considering it fluid....

Thanks for the PR dear @cjpearson Removing multi-line comments without AST awareness can be unsafe this is why we don't it. See https://github.com/unjs/mlly/pull/56 for some context. Until https://github.com/unjs/mlly/issues/219 arrives, if...