Feedback: Railpack
Today we are pleased to finally release our new builder into Beta - Railpack - https://railpack.comBuilt to replace Nixpacks, but with none of the downsides, it's everything we originally hoped Nixpacks would be and so much more -- First-class support for SPA apps (Vite, Astro, CRA, Angular)- Better caching, faster, more efficient builds, and smaller image sizes - 38% (Node) and 77% (Python)- Unlike Nixpacks, updates to Railpack itself are not needed to support the latest version of anything, this means the latest version of bun is always available- Railpack will cache the last working versions for a deployment and use it for future deployments so updates to Railpack defaults won't break deploys- Better verbosity with the build plan, we now tell you the exact versions of the language, and where the version was retrieved from- We now use mise for package resolution and installation, Nix is not used anymore, it's just not a good fit for the needs of a buildpack- Built-in language-specific help outputs for common errors such as "No start command was found" - we now tell you exactly what to doIt is still in Beta so there are some things to keep in mind -- There is no Nixpacks compatibility layer, if you had a custom Nixpacks plan, then it would essentially be ignored by a Railpack build- We don't yet have language parity with Nixpacks, only Node, Python, Go, PHP, Java, Deno, and Staticfiles are supported at this time- There is no way to specify Nix packages to install during build, and there likely never will be- The Railpack documentation is still a work in progress, but it's built with Astro and starlight for the curious- We are switching from Rust to Go to have better interoperability with buildkit, which gives us better control over the build, no more intermediate Dockerfiles- We have a railpack.jsonconfig file - But the syntax is yet to be finalizedIf your language is supported and you are eager to try it out, you can switch to the new builder from within your service settings under the build section.And be sure to read up on the documentation we have so far so you're caught up on anything I haven't mentioned here!