2 years ago
Hello, so I got this error earlier today where it says I don't have needed TypeScript dependencies installed. This error only occurs on redeployments or restarts, if you create a new instance it works perfectly. I think it has to do with the docker container or next js's cache (.next), is there a way to clear it or is there something I can do? I originally had a container that I've been using for about a week and out of no where this error occurred, I made a new service with the same configurations and it worked until it redeployed for a new git commit. I'm really not sure what the bug could be but cache. I have redeployed multiple time and new services and the issue persists.
22 Replies
2 years ago
Are you using nixpacks?
Yes
2 years ago
Try setting a service variable
NIXPACKS_NO_CACHE=1
I added it and I am getting the same error
2 years ago
Try
NO_CACHE=1
Unfortunately the same error
2 years ago
Can you show me your service variables please
I showed the non important vars but I kept the important ones hidden, do you need me to show every value?
Attachments
2 years ago
Thats exactly what I wanted to see, that looks good to me.
If this isn't a cache issue, what else could it be?
2 years ago
Thats exactly what I wanted to see, that looks good to me.
If this isn't a cache issue, what else could it be?
Could it be a issue on my end? I can make multiple services and the first build works but anything after that, restarts, redeployments (git commits), etc. The build fails and throws I need to install TypeScript dev dependencies. The reason I thought it had to do with cache was because after the first build is initialized it crashes and throws a exception.
2 years ago
Did you want to try out the beta V2 builder and V2 runtime so that we can rule out an issue with railway? they can both be enabled in the service settings.
2 years ago
Did you want to try out the beta V2 builder and V2 runtime so that we can rule out an issue with railway? they can both be enabled in the service settings.
I have these configurations set from my last service
2 years ago
But are they both enabled on this service?
I believe so, you are talking about these correct?
Attachments
2 years ago
Yes, does your service have a volume?
No
2 years ago
Then this would be an issue on your side.
Hm okay, I'll try my best to debug it then. Thanks for narrowing down the debugging process for me though, I appreciate it a lot.
2 years ago
Happy to help! Keep me updated!
I retraced my steps, I went through around 100 commits on my GitHub history and couldn't find what could break the entire application with this weird bug. I then turned off the beta v2 builder and switched to legacy because yesterday (6/12/24) I turned these new configurations on in the morning and that's when the issues came up. After turning off these configurations all builds, restarts, and redeployments now work.
2 years ago
The team would need a minimal reproducible example if they where going to look into this.