build

[yaaaaaaaaaaaaaaaaaaaaimn]

It would be very nice if you could give us a version that is already BUILT.

[Enchoseon]

Every argument for a building process—which is just bundling and transpiling an interpreted language—does not apply to this project:

1. Ease of Distribution: The lack of prebuilt releases is a feature to improve the quality of bug reports.
2. Simplified Deployment: The "building" process isn't prohibitively complicated or expensive. You don't need to compile with a specific version of GHC, you can run this on a Raspberry Pi. The most "expensive" part, which is just downloading the dependencies, only happens once per system/partition if you use pnpm.
3. Protecting Source Code: This project is open-source and catered to programmers and tinkerers.
4. Offline Usage: This project is a proxy meant to be used online, and you can use it offline after downloading the dependencies from the internet with as much ease as downloading the project.
5. Cross-Platform Compatability: Node.js is already cross-platform compatible.
6. User Experience: This is a poweruser CLI application, there isn't any user experience benefit.

Additional reasons I don't provide builds:

1. Bloat: Bundling an entire runtime and its dependencies à la Electron bloats filesize and makes updates a matter of redownloading the bloated executable in whole. A build process also bloats the codebase.
2. The lack of prebuilt releases is a feature to improve the quality of bug reports.

In short, a build process isn't within the goals of this project and the lack of one is a deliberate decision to improve the quality of bug reports. Thank you.