Hello,

since it started breaking today it's likely a railpack regression on their end, not your config. the safest fix to try right now is to remove npm:@posthog/cli and npm:eas-cli from your mise config and just install them manually in your build command with npm install -g @posthog/cli@0.6.1 eas-cli@18.3.0 before your actual build runs. node is already installed by that point so npm is available. let me know the result

Hope this help you :)

i will detail more my answer, so basically what you need to do is stop relying on mise to install your npm cli tools and do it yourself manually in your build command instead

go to your mise.toml and remove these two lines: npm:@posthog/cli@0.6.1 and npm:eas-cli@18.3.0

then in your build command (wherever you have it set in railway, like in your railway.toml or service settings), just add this at the beginning before your actual build runs: npm install -g @posthog/cli@0.6.1 eas-cli@18.3.0

so if your build command was something like "bun run build" it becomes "npm install -g @posthog/cli@0.6.1 eas-cli@18.3.0 && bun run build"

so by the time your build command runs, node is already fully installed by mise, so npm is available and can install those packages without issues. you keep node and un in your mise.toml, you just stop asking mise to handle those two npm packages since that's where it's breaking.

Thanks for your input. I'm aware of how to work around the error, but more interested in Railway's confirmation that this indeed a Railpack regression.

totally get that, but waiting on railway to confirm or not, the workaround fully solves the issue in the meantime, i hope i helped you fix it :)

This issue persists, but I've worked around by moving my dev-only cli tools that was causing the issues to mise.development.toml. I still am convinced this is an issue with Railpack and/or Metal build environment. I'll keep this issue open for now and hopefully we'll get a response from Railway

since the workaround with mise.development.toml actually fixed it, thats the right move for now. if you want an official confirmation from railway that this is a railpack issue, best shot is to open a github issue directly on github.com/railwayapp/railpack with your log and you'll get a proper response

It looks like Node.js and npm are getting installed, but during the same build step, npm isn’t available in the PATH yet because of that when mise tries to install packages like posthog/cli or eas-cli it fails saying npm not found or no such file. This usually happens in CI/build environments where the shell doesn’t reload after installing Node or mise shims aren’t activated properly before the next command runs