4 ms·
You can't, and for good reason. Deno has slightly different API's than Node. Bun also has subtle differences between their STL implementation and Node's, but af
by selfmodruntime 3y ago
You can't, and for good reason. Deno has slightly different API's than Node. Bun also has subtle differences between their STL implementation and Node's, but afaik, they're getting there.
- apitman 3y agoI think maybe I was unclear. I'm talking about writing libraries that abstract across these differences and provide a single API, as sibling describes. I already know it's possible. I made a simple filesystem abstraction here[0] and a very simple HTTP library that uses it here[1]. They both work in Node/Deno and the browser. Unfortunately I ran into issues with Bun's slice implementation[2], but that should be fixed eventually. My overall question is that I suspect there's a much better way of detecting and using the different backends, and I'm wondering what techniques are out there. [0]: https://github.com/waygate-io/fs-js https://github.com/waygate-io/fs-js [1]: https://github.com/waygate-io/http-js https://github.com/waygate-io/http-js [2]: https://github.com/oven-sh/bun/issues/7057 https://github.com/oven-sh/bun/issues/7057