Getting deployment error:

try deleting your yarn.lock file and run yarn install then push your changes

@Brody we tried it and it didn't work 😦

did git tell you that there was changes made to the lock file?

I believe so but I'll try it one more time

what yarn version are you using locally, and what yarn version is railway using? (it should tell you in the build table at the top of the build logs)

I see Nixpacks v1.13.0
I don't see yarn specific version

screenshot please

my local yarn version is 3.2.0

and just tried again , failed with same error msg

you see there, railway is using yarn 1x

ohh .. I wonder why it was building fine all this while haha
this thing started recently

try adding this to your package.json

 "packageManager": "yarn@3.2.0"

within the dependencies object right?

no
root object

should I delete yarn lock again and rebuild?

couldn't hurt, make sure you run yarn install though, and also make sure the file as been uploaded to the repo

didn't work 😦 same error but looked slightly different

the first screenshot has the package.json file wehre it says packageManager 3.2.0

okay that worked for now, I'll let ya know if it happens again. Thanks @Brody ❤️

@Brody sorry to bother you again .. we are not having the same issue but sometimes when we push to a branch it doesn't trigger a build. I noticed that previously too and didn't know if the issues were related. We are currently using this in package.json

"scripts": {
"start": "serve -s build",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject",
"preview": "react-scripts start"
},

"devDependencies": {
"@types/lodash": "^4.14.197",
"@types/react-datepicker": "^4.15.0",
"@types/react-lottie": "^1.2.6",
"serve": "^14.2.1",
"tailwindcss": "^3.3.3"
}

is there a limit on the number of builds per hr or something?
oh it just triggered but a few mins late and not instantaneously as it was doing it before .. is it a lag in the system?

github is having issues
https://www.githubstatus.com/

ahh cool cool thanks @Brody 🙂

no problem