#npm install --force
58 messages · Page 1 of 1 (latest)
N/A
add a nixpacks.toml to your project with this in it
[phases.install]
cmds = ['npm install --force']
Cheers, not in the src right?
Like where you add the netlify.toml?
root of the project, yeah
I'll try it, nothing else needed?
nope that should be it
Hmm now it deploys at least, weird though because it doesnt seem to resolve a component which exists... which cuases the deploy to break
care to send the specific error message youre getting?
make sure the folder and filename casing is the same in github as it is locally
that would do it
I hope
i assume you dev on windows? windows is not case sensitive
Yes, me and my devPartner been having a fight with this project. We changed the names once of the components and now its a mess. Although he made a new rep yesterday which should be fixed 🙂
Can it fail beause of these type of noused?
what kind of app is this?
MERN
I meant specifically what is this you are currently trying to deploy
looks like a frontend app? but more specifically?
Frontend fintech kind of
I was setting upp deploy with heroku backend + netlify frontend earlier but wanted to shift towards railway 🙂
React indeed.
create react app
then two issues here.
you have warnings and they are being treated as errors thus causing your build to fail, you have two options, fix the warnings, or ignore them so they don't cause your build to fail.
second issue we will get to after this.
I will fix the warnings in shortterm and unused variables.
just a lot of code to clean up and my buddy will handle that
It's been working great to host on local
How can i ignore them?
When building here?
set a service variable CI to false
and the second issue.
from what I can tell, you're trying to run a development server on railway, since create react app is only capable of running a development server
simple enough fix, let's tackle that
https://github.com/brody192/create-react-app-starter
copy the nixpacks.toml and Caddyfile from this repo into yours
I'm pretty sure you won't need npm install --force since the real issue was that one file named incorrectly from what I can tell
like this?
I think it's a lowercase F
Ofc.
I'll leave this to my backend partner, i suck at this stuff
now its loop deploying at least
have you copied in the two files I asked you to?
no, just copy those two files into your project
please copy the Caddyfile to your repo
Oh yea i did add the file, and pushed
and does it work now?