R
Railway•3mo ago
rdil

Caching causes build to get significantly longer

I have a build which is for a decently basic Nest.js app with Node and TypeScript. I'm using yarn 4.1.1 as a package manager, and i've recently found something really strange. Modern yarn projects don't support caching by default within nixpacks, so I tried adding cacheDirectories to my package.json to cache .yarn/cache in my project. After adding it, the build time went from ~20 seconds to ~5x that. Not only that, but the publish time seems to roughly 10x what it was before (lasting 264 (!) seconds). I'm not sure exactly what's going on but it's not good and I figured I'd ask about it here.
1 Reply
Percy
Percy•3mo ago
Project ID: c0e3b2af-8f03-40c2-85e3-30ac2bf30ceb
Want results from more Discord servers?
Add your server
More Posts
[SOLVED]Does railway run on kubernetes? If so can I use the API for the current pods that are onlineDoes railway run on kubernetes? If so can I use the API for the current pods that are online? Or cLaravel 11Hello [Provider's Name], I hope you're doing well. I'm experiencing some issues when trying to deplIs there way to have Github Action fail if `railway up` failsSo I have a bit of a custom setup which requires me to use Github Actions to publish to railway, it'Backend API response is slow even though not using max limitsRailway metrics says we have a max of 8 vCPUs. The max we're using is only 2.6 vCPUs. But we're stil