Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment: PaaS default nodejs version #28621

Closed
3 tasks done
Crn0 opened this issue Aug 13, 2024 · 3 comments · Fixed by #28720
Closed
3 tasks done

Deployment: PaaS default nodejs version #28621

Crn0 opened this issue Aug 13, 2024 · 3 comments · Fixed by #28720
Assignees

Comments

@Crn0
Copy link
Contributor

Crn0 commented Aug 13, 2024

Checks

Describe your suggestion

Add a note that some PaaS providers do not default to the LTS version of Node.js (e.g., Railway defaults to Node.js 18). Depending on the Node.js features you are using, you may need to explicitly specify the Node.js version in your package.json file.

Path

Node / JS

Lesson Url

https://www.theodinproject.com/lessons/node-path-nodejs-deployment

(Optional) Discord Name

No response

(Optional) Additional Comments

No response

@CouchofTomato
Copy link
Member

Would this not be covered in the setup guide for the service itself which the user should follow?

@Crn0
Copy link
Contributor Author

Crn0 commented Aug 13, 2024

I don't know about the other services, as I used Railway, but I don’t see the default Node.js version being mentioned there. Essentially, you can deploy your GitHub repo directly. Their quick start tutorial uses Next.js and Prisma (I started this project before the revamp), and they’re also installing the Railway CLI, which I think is out of scope for ToP. I’m not sure if it will make sense now given the revamp. It is also not mentioned which Node.js version is used.

Knowing the default Node.js version and whether it is an LTS version would be helpful, as my app broke due to Railway defaulting to Node.js version 18.x.x, which does not support a feature I used in my app.

@KevinMulhern
Copy link
Member

Thanks @Crn0, a warning note sounds like a good idea. I've assigned it to you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants