Bundling support

[tiziodcaio]

@yao/pkg work is great but has some performance issues: why should I download a huge binary bundle with tausands of kilobytes occupied by nodejs when I can simply depend on the system one? I might use the time spent downloading lando binary installing nodejs itself, if I could try to not bundle it.
I was trying locally the bundling with esbuild and alternatives like rollup to output a single .JS file with other support files (like it was done in the actual build system)
The experiment is promising, maybe soon I'll try to commit a PR

[pirog]

because its unreliable asking the user to install the correct version of node. its preferable to ship a single executable in production for all kinds of reasons and its highly doubtful that will change. if you want the model you are describing you just install and run lando from source which is what we do for development.

that all said, there is a best of both worlds approach here which would be to introduce a bundler as you suggest so that the resulting packaged up build is significantly smaller.

[tiziodcaio]

Maybe trying bun? They support bundle natively

[AaronFeledy]

Bun is pretty good, but doesn't currently support all of the Node APIs that Lando uses (or at least it didn't when I checked a few months ago).

[AaronFeledy]

That's not excluding it from potential use in the future as its definitely worthy of consideration. I like that it runs TypeScript(coming to lando 4) without transpiling, supports importing ESM and CommonJS without conflict, and has a built-in packager for generating single-file binaries. Its runtime also has a number of performance improvements over Node.