Idea from @sigmaSd

[Pinta365]

This idea was lifted as part of a package issue. Moving it here so we can discuss.

I have a suggestion, what about creating a new module @cross/cross that exports a class Cross that have a similar api as Deno, but internally it works for multiple runtimes (Cross.readFile, Cross.readTextFileSync, etc)

Originally posted by @sigmaSd in cross-org/dir#2 (comment)

[Pinta365]

Basically this is the whole idea of the cross-org project, filling the cross-runtime gaps of @std/ on JSR.io which is a new package registry with excellent cross-runtime support.

Our approach has been to split things up in smaller packages instead of a "cross" module though but the ideas is the same.

For the examples you are mentioning we started with a fs module but decided to use the node:fs compatibility layer that is available in Deno, Bun and Node.js instead. We might bring new life to that idea though and use the runtimes native functions.

Are there any other specific features you are eager to get us working on @sigmaSd?

We are also very open to involve more like-minded developers so feel free to open PRs to our projects or come with new ideas.

[sigmaSd]

This cross runtime story is a definitely new thing, so I'm still playing around with it.

I understand your approach, I just mentioned this idea because maybe it makes porting deno projects to cross easier, so instead of Deno.serve Deno.args, etc, I just swap Deno with Cross (or X ?) and now it works on multiple runtimes just like that.

For new features maybe Deno.dlopen would be great, it will allow projects using plug to work easily on other runtimes, I have an issue open already denosaurs/plug#36