Failing to spin up default template Next Prisma tRPC
Hello there peeps! I'm trying to spin up a Next Prisma tRPC template from scratch, but sadly the defualt template fails in the fronted deploy step, due to a npm conflict: While resolving: eslint-config-next@11.1.2
Find it odd that a default template would fail - what could be wrong here?
Project ID:
fa498e03-4d11-491e-8620-bcb80fb6f8c610 Replies
Project ID:
fa498e03-4d11-491e-8620-bcb80fb6f8c6You might find these helpful:
- Trying to build next-prisma-trpc starter and getting a build error.
⚠️ experimental feature
Try setting
NIXPACKS_NODE_VERSION=14How do I do this? Is this an environment variable ?
Ye
In the environment tab on the website
Ahh, I see the frontend module had its own "variables" section. I wasn't aware.
Ye
I found a ton of issues with this template in general. It is very outdated and doesn't work out of the box at all. IMO railway should either maintain it or remove it.....
I hope this will helpe anyone facing the same issue:
- keep latest version of node
- update all other dependencies that are causing troubles to newest version
This can be done by cloning your report from github, then run
npm outdated to see what the latest version of the dependencies are. The ones are are causing issues should most likely be updated. In my case it was eslint. I updated it by running npm install eslint@8.30.0 --save-dev which was the latest version as of today 22nd Dec. 2022.
I then run git add . followed by git commit -m "updated esling" followed by git push which pushes the changes and triggers a new build.
I then got a new error, and followed the same pattern... updating the dependency that were causeing an error, and eventually after a few roundtrips the build suceeded.
Note: use --save instead of --save-dev if the dependecy you are updating is listing under "dependencies" and not "devDepedencies"
Cheers ✌️Thanks for this. I'll see if I can't update this at some point
can you try again
just fixed it