failing to redeploy
Hello, is anyone else having issues with deployment? I am failing to redeploy projects that were successfully deployed yesterday.. in fact, all builds which were successfully deployed yesterday are failing today.. please let me know what more information I can provide for support, thank you!
47 Replies
Project ID:
cf12f7ff-685e-497d-bca7-99641a7cffd5project id is cf12f7ff-685e-497d-bca7-99641a7cffd5
is your build using nixpacks? if so, what version. this can be found at the build table at the top of the logs.
what is your tech stack?
please also provide full build logs a long with all this info
backend is node express and frontend is javascript react
I have not updated or changed anything from last night.
okay well let's focus on one at a time, what would you like to tackle first?
just the deployment for now.
this is the logs from when the build successfully deployed yesterday
whitch deployment, the frontend or backend
oh sorry, front end
what text file pertains to the failed build logs for the frontend
the first text file is the failing logs and the second file is when i was successful with deployment. both the same exact build
neither of those text files are full build logs
but either way, did you update any dependencies?
no
sorry but how do I get the full build logs?
don't worry about it
send me the table at the top of the failed deployment
╔═════════ Nixpacks v1.5.1 ═════════╗
║ setup │ nodejs-16_x, npm-8_x ║
║───────────────────────────────────║
║ install │ npm i ║
║───────────────────────────────────║
║ build │ npm run build ║
║───────────────────────────────────║
║ start │ node index.js ║
╚═══════════════════════════════════╝
and send the same from the deployment that worked
╔═════════ Nixpacks v1.5.1 ═════════╗
║ setup │ nodejs-16_x, npm-8_x ║
║───────────────────────────────────║
║ install │ npm i ║
║───────────────────────────────────║
║ build │ npm run build ║
║───────────────────────────────────║
║ start │ node index.js ║
╚═══════════════════════════════════╝
why is install defined as
npm i that is not the default
and are you sure these are from the front-end? can you send me your repo for the frontend?sure one moment
GitHub
GitHub - 88joonyc/ticker-app
Contribute to 88joonyc/ticker-app development by creating an account on GitHub.
okay, I'm just about to have lunch, will look at that and get back to you with hopefully good news
Sure, appreciate the help! have a good lunch!
can you build this app locally?
npm run build
because i cant build it locally, and if i cant build it locally, the issue isn't with railway
this commit does compile
https://github.com/88joonyc/ticker-app/tree/c1bbe9a415d65fce5f0a8bdcddaf7e8035b01bc9
but there are other issues, like you are still using the default start script at this pointhi, yes, I've been building the project locally each time to deploy.
sorry, I may take some time to respond.. have an interview in about 20 mins
what node version do you use
v14.21.3 ahh i'm guessing my terminal reset
whats that about your terminal?
terminal is using 14.21.3.
okay
so i see that your repo lacks a package-lock file and it did have a build folder though you just deleted that
why the lack of lock file?
i'm actually not sure.
add the build folder to your .gitignore, you dont want to be committing the build folder
and provide a package-lock file
roger
getting the same error
sorry but i'll brb
yes, i am still looking into that
good luck on your interview!
says its something to do with webpack? not sure but here is what i see again
thank you!
i still cant build your app with node 14.21.3
what command do you run to build your app locally?
hi, I'm back but I have another call soon.
for some reason, i was unable to run the build locally.. im guessing it was due to node version? so i installed node v16.16.0 and now i can build locally. I'll try deploying to see if it work.
it does not build with node 16.16.0 either
i can build locally but i had to reinstall dependencies after deleting the package-lock
?
npm run build
sorry that one flew right over me
okay i got your app to build
cloned your latest commit
changed your start script to
node index.js
ran npm install --package-lock-only because your lock file was out of sync
added engines.node = 16 to the package.json file
deployed, and it worked
https://test-service2.up.railway.app/OK, I'll try that as well.
Thank you, that worked for me as well!
awesome, very odd though