Skip to content

Latest commit

 

History

History
15 lines (9 loc) · 1.69 KB

WHY.md

File metadata and controls

15 lines (9 loc) · 1.69 KB

From the very first available public releases I've always been amazed by runjs!!!

Up to version 1.15.1 (included) there was one really useful feature: the ability to manage npm packages from within the app, and those where only affecting the app context, really useful feature. I use(d) it to quickly try something and check the result as a small javascript playground to validate small things.

The updates are forced (regardless the auto-update preferences, indeed being a non certified app you have to accept on the usual modal that appears when you start such unverified apps for the very first time), and whenever a new version is available there is no apparent way to avoid the update. Actually I discovered how and it's quite straight-forward (let me know I u need to know, I dont really want to write it here), thus I still can run the last free useful version of runjs, but somehow I started to feel itchy about runjs.

The point is that the author switched into a yearly based subscription for some features among which the node_modules manager (the only one truly relevant for me). Really a miserable move, such a shame.

Aware that runjs was developed using ⚡️ electron js, I started investing some time developing something similar, aiming to the features I was used to have for free in runjs, but quickly after getting there I realized the right thing was to tune my aims. For the moment I keep the sourcecode in a private repo but the build .dmg file is instead in a public repo; also for the moment I only build the MacOS version.

In case you could provide some feedback it would be outgareously great for me.

Only love can save us! ✌🏽