This appears to be an issue with the node nixpack and upgrading from bun install 1.0.11 to 1.1.8.

Having the same issue here.

UPDATE: adding this to nixpacks.toml fixed for me

[phases.setup]
    nixPkgs = ['...', 'python3', 'gcc']

nixpacks.toml

providers = ['node', 'python']

railway.toml

[build]
builder = "NIXPACKS"

buildCommand = "bun run build"

nixpacksVersion = "1.21.3"

Please provide your build logs for your first build that started failing and the build that had previously worked -

https://bookmarklets.up.railway.app/log-downloader/

Thanks for these reports. This seems to be an issue with the latest Bun and Node 20. We will be looking at this more deeply on Monday. In the meantime you can downgrade Nixpacks version as outlined in the railway.toml file here https://help.railway.app/questions/suddenly-unable-to-build-due-to-not-find-70b6dd3a#p-4. Or (preferred) install python3 as shown in the nixpacks.toml file here https://help.railway.app/questions/suddenly-unable-to-build-due-to-not-find-70b6dd3a#p-3.

Any update to this @jr?

Hi @r-k-h,
Sorry for not getting back to this thread sooner.

The latest Nixpacks version (1.24.0) should work out of the box with Bun and Node 22 (I've just confirmed). If you are seeing issues with a specific package.json dependency that requires python, you can add the Python provider in the service settings or use a nixpacks.toml file. Nixpacks Python support was recently updated to use 3.11 as the default version which is much newer and more up to date then the previous default of 3.8, which I suspect is why you were having issues.

I recommend updating the Nixpacks version to 1.24.0 and kicking off a new build. If there are still issues we can take a look at specifically what is causing the build to fail when if occurs.