pkg

Any consideration to packaging this as a portable archive that can be extracted and executed easily (e.g. w/ like pkg [0])? While adoption may not be a goal, asking users of software to obtain it from a JS package manager is a bit much. Don't underestimate the value of a download button/link. 0 - https://github.com/zeit/pkg

TL;DR: this is like Electron, but instead of bundling Chrome it uses the local Chrome installation. pkg is recommended for bundling the Node app so I imagine the bundle includes V8 and Node. https://github.com/zeit/pkg

I'm on mobile, but do you have an example of bundling a node app somewhere? I'm curious how it compares to using something like pkg [0]. [0] https://github.com/zeit/pkg

Clickbait. At least propose what it is that you think needs to be done to address this so-called chaos. Worth noting that ES2017 added String.prototype.padStart and String.prototype.padEnd. The whole left-pad thing is blown out of proportion. Second, you shouldn't be relying on npm for deployments. You dig your own grave. If package deletion is a concern, then host a mirror with something like Nexus [0], or pay for a service [1] [2] to do it for you. Over the years there have been a few local npm mirror tools [3], but I don't think any of em have really caught much traction. There's also the option of bundling each release. For that you can use a tool such as Webpack [4], or take it one step further and generate a single binary using something like pkg [5]. Developers also have the option of forking their dependency graph and updating ref

https://github.com/zeit/pkg can package up Node projects into a single executable.

We also have some tools we use with the Heroku CLI we will be backporting into oclif very soon that directly addresses this problem node has with distribution. Essentially it's some scripts that let you export an oclif CLI as a standalone tarball (node binary into it), optionally being able to autoupdate with github or s3. oclif is also compatible with pkg (https://github.com/zeit/pkg) which will turn the CLI into a dependency-less single binary just like it would be with Go. I don't like it personally as I find it useful for debugging to actually edit the files. With Go we would have to cut a release just to add extra debugging information.

Check out something like pkg by zeit[0] which compiles the node app to a binary. Then put it in a directory in your $PATH and you'll be able to run it as `fibonacci`. [0]https://github.com/zeit/pkg

If you want to build interactive terminal interfaces, check out blessed [0]. Even better, you can use react-blessed [1] to write declarative UI code! You can also find additional widgets in blessed-contrib [2]. For actually shipping the code around, you could use pkg [3] to generate a single binary. That lets you avoid having to install node or any supporting libraries. [0] https://github.com/chjj/blessed [1] https://github.com/Yomguithereal/react-blessed [2] https://github.com/yaronn/blessed-contrib [3] https://github.com/zeit/pkg