Hey, the error you mentioned is just a warning and won't effect anything, I took a look at your build logs and it seems your error is:

#10 2.141 npm ERR!
code EUSAGE
#10 2.145 npm ERR!
#10 2.145 npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
#10 2.145 npm ERR!
#10 2.145 npm ERR! Invalid: lock file's typescript@5.5.2 does not satisfy typescript@4.9.5
#10 2.145 npm ERR!
#10 2.145 npm ERR! Clean install a project

Essentially, you just need to resynchronize your lockfile, which you can do by running npm install and then committing again

@Fragly okay.. I'll do that.. thank you

@Fragly I just need to reinsall react again on the client side?

You just need to run npm install on your side to resync the the package-lock file

Also if you're using react app then I'd recommend you copy the Caddyfile and nixpacks.toml from this repo by Brody into your repo:

( or if you're using vite then just do the same with )

This just ensures you're running it properly on Railway

sorry to bother you.. should i run the npm install at the root or in the client folder?

@Fragly Thank you for assisting me, with the project. I removed package-lock.json and it was able to deploy. But when I typed npm install to create a new package-lock.json and pushed a new version it failed. Also should I create a new thread

We can keep going in this thread, can you share your build logs?

sure..give me one moment

sorry to bother you on this

no worries!

1272956068778999880

It's still not synchronized D: this time it's even more unsynchronized cause there's a whole dependency missing too now

awww nooo

how do you see it

If you did run npm install and then didn't change anything in your package.json afterwards which may have lead to it losing synchronization again then I'm wondering if you're not perhaps gitignoring the lockfile and github is now just storing a super duper outdated lockfile 🤔

in your build logs:

#11 2.359 npm ERR!
code EUSAGE
#11 2.365 npm ERR!
#11 2.365 npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
#11 2.365 npm ERR!
#11 2.365 npm ERR! Missing: fsevents@2.3.3 from lock file
#11 2.365 npm ERR! Invalid: lock file's typescript@5.5.2 does not satisfy typescript@4.9.5
#11 2.365 npm ERR!
#11 2.365 npm ERR! Clean install a project
#11 2.365 npm ERR!
#11 2.365 npm ERR! Usage:
#11 2.365 npm ERR! npm ci
#11 2.365 npm ERR!

i do have a .gitignore in my client folder

is it set to ignore the lockfile?

https://github.com/rdelva/fullstack_app <-- thats my github

oh cool, this certainly makes it easier

🙂

the lockfile isn't in there though.. just other stuff.. but i'm not sure that would cause th eissue

yea, you're not gitignoring it, I'm pretty confused now 🤣

no worries.

I did use typescript on the api side

but not in the client side

and both folders both have there own package-lock.json file

wait.. I looked at my api thing.. no I didn't 😦

While I'm looking through your project, I'm noticing a lot of things that is very bad to do in production:

1. in the API side, you're running the API using nodemon, it's very very bad to do that in production, run your app using node instead

2. in the API side, you're running npm i on build, you don't want to do that. Railway will install dependencies for you

3. in the API side, you're pushing your SQLite database to github, this is bad because it means once deployed, it won't persist through redeployments and it's a security vulnerability. This db includes passwords and your github is public 😬 you should consider getting rid of it ASAP. For future, you'd want to load your SQLite database into a volume using Filebrowser and then use it through there

4. your Caddyfile and nixpacks.toml was supposed to be thrown into the client side of your app, not in the root

as for the current problem you're facing, it's definitely an issue with desynchronization between your package json and package lock json.. I'd recommend you try running npm install --package-lock-only again on the client side. if it still doesn't work after that then I'm out of ideas..

Useful resources:

• -

thank you. I'll defintely making adjustments. Unfortunately this was from a teamtreehouse final project and the final part of it was to learn how to deploy it on railway

No problem!! What node version are you using locally?

i'm not sure.. its been a minute since I last checked

one moment

Node.js v16.13.2.

Version mismatch could be a probem.. Railway runs Node 18 by default, you can change the version railway uses by setting the engine in your package json files or just upgrade to node 18 on your side before regenerating the lockfile

nods

k.. I'll do that..

Good luck :D

thank you again… if I'm stuck again..am I better off rebuilding and recreating everything again

I'm sure the app itself is fine, the issues I mentioned above are easy fixes luckily.. well except the public database one - that's practically unfixable, well you can fix it but it's gonna be hard to remove the damage since the creds will be in the github repo and you'll need to remove each commit containing it

the public database is fake.. they did it for learning purposes. But you do have a valid point that this isn't the best way to do it.

ohh okay, I had a feeling that was the case

Deployment was successful but the logged changed 😦

should I create a different thread for this?

1272975836487880714

I think you might've made your start command a build command on your service settings, just need to remove that

okie..thank you

VICTORY!!!!!

well almost something

https://tenor.com/view/happy-guy-dancing-black-guy-gif-26630157

Awesome!!! Happy to hear

thank you so much.. your patience with me.. .

of course <:SmileFluent:865334941150871592> it was no trouble at all

just one more thing.. int he future..whats the best way to prevent the desyncronization of the package-lock.json

In this case it likely was the version mismatch that caused the problems, prevention for that would just be to specify your node version in packagejson at all times

Although to prevent that desynchronization, just don't edit dependencies or dependency versions straight from package json - use commands instead, or if you do edit it directly then just synchronize it again with npm i

nods

understood.. have a wonderful day and bless you 🙂

Thank you, you too :)