js-dos VS wasmer-js

Funny timing. I actually just built an in-house server this past Friday to host the original Oregon Trail using js-dos because I don't like poking holes in the content filter for sites like archive.org. I didn't worry too much about copyright, as I assumed it was abandonware at this point.

Thanks glad you liked it! It's actually not a port but is running on DOS via https://js-dos.com/, same as Doom and Jazz Jackrabbit. I actually have my 8 favorite Shareware games on my website which can all be played.

https://dustinbrett.com/?app=FileExplorer&url=/Users/Public/...

Maybe something like https://js-dos.com/ for dos and https://www.emulatorjs.com/ for old game consoles?

DOS Emulation via js-dos

Adding emulators is something I always wanted to do and I have plans to add more in 2022. For 2021 I was able to add Virtual x86 (.img/.iso), BoxedWine (.exe/.zip), JS-DOS (.exe/.zip) & Ruffle (.swf/.spl). Most of these emulators utilize WebAssembly to run non-JS code.

It can indeed run some real windows programs via BoxedWine. I've set it up so you can double click an .exe and it will automatically try and run it, although typically if it needs support dll's then they are all in a zip. For example the zip file for Notepad++ 32-bit x86 can directly run in BoxedWine. You just drag the zip file on, right click and select run in BoxedWine. It can also run DOS apps/games via JS-DOS and has similar mappings for exe/zip. Both emulators make use of WASM as do several other apps, such as the x86 emulator shown in the demo video. My main "OS" is only JS/HTML/CSS written in TypeScript with React/Styled Components.

});

I was then able to just use this code example with one caveat (https://github.com/wasmerio/wasmer-js?tab=readme-ov-file#use...)

I had to update the SDK import with crossorigin="anonymous"

I use https://github.com/wasmerio/wasmer-js and while v0.12 works fine, v1.2 never returns and is stuck in a busy loop internally somewhere. I did not bother bisecting it because the API changed at v1.0.

You can run WASI/WASM modules in the browser using e.g. the (rather simplistic) official WASI polyfill or the more fully-featured wasmer/wasi. So while htis is certainly a bit more combersome than a direct JS FFI, you should already be able to interact with WASI/WASM-compiled Haskell code from JS.

Good spotto! That's the WASI runtime from wasmerjs (https://github.com/wasmerio/wasmer-js).

That's not the WASI runtime being used in this playground. The one in this playground is @runno/wasi-motor (https://github.com/taybenlor/runno/tree/main/packages/wasi-m...). I haven't released it as an NPM package, but it's all MIT so feel free to copy it.

WASI Modules via Wasmer JS

I have good news! Wasmer can also be run on the browser. Check out wasmer-js [1]

[1] https://github.com/wasmerio/wasmer-js/

Maybe wasmer-js could be used by Deno to provide WASI support inside their engine? :-)