Thanks for the update - yes, sadly I have seen it. They've totally screwed Espruino users over.

Unfortunately I need access to USB Serial devices, and Web USB doesn't appear to allow this. I've filed a bug here that'd be good to get some noise around: WICG/webusb#56

If it works, it would be pretty cool - negating the need to have a Web App at all. However I'm not inclined to put much effort into that in case Google decide to kill Web USB at some point too (which feels super-likely).

So while Service workers would be cool (and might be added for Puck.js and Web Bluetooth), they won't actually help here unless Web USB changes to allow other devices to work with it. Quite a few users need decent filesystem support too, and there's no way to get that working for them under a non-web-app system unless I write plugins (and again, I'm not inclined to spend much time on a Chrome-specific plugin unless Google kill that later on as well).

A while back I got a bit scared by the total lack of effort going into the Chrome Serial API, so I decided to come up with a plan B. As such there is an Electron-based version of the Web IDE now: npm install espruino-web-ide - however that's obviously not going to work on Chrome OS.

So it's not the end of the world. It's still not great though - I'll need to create and keep up to date installer packages for Windows and Mac, which is way more effort for me (effort which should be spent making Espruino better). It also sucks for users, as it's now definitely not a one-click install (and will cause problems for the Schools using Espruino)

Update on this - Chrome app support officially ends June 2020 now: https://chromeunboxed.com/google-announces-timeline-for-the-end-of-chrome-apps-on-chromebooks/

Web Serial support has now been added (by Reilly Grant at Google!) so actually we're good to go with http://espruino.com/ide

Also there is an NW.js port as well, which is available from http://www.espruino.com/Web+IDE

I tried "Installing from GitHub (Latest Version)" -> "Running in Chrome"

Which rendered this in the browser:

This was tested running on Fedora Linux 38, kernel Linux 6.4.4-200.fc38.x86_64, Cromium web browser 114.0.5735.198.

I suggest ripping this "Running in Chrome" section out, or adding a disclaimer at the top of it.

Thanks - just updated the readme