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

🧹 Node 16 has reached End-of-Life! Long Live Node 18! #1879

Merged
merged 9 commits into from
Oct 11, 2023

Conversation

zspencer
Copy link
Member

Per https://github.com/nodejs/release#release-schedule, Node 16 is decommissioned! This bumps us to the newest LTS, Node 18! Hooray!

Make sure to delete your node_modules folder, since I have no idea how any of this works but I expect that keeping old node modules around is bad-idea-jeans.

@zspencer zspencer requested review from a team October 10, 2023 00:04
- #892

Per https://github.com/nodejs/release#release-schedule, Node 16 is
decommissioned! This bumps us to the newest LTS, Node 18! Hooray!

Make sure to delete your `node_modules` folder, since I have no idea how
any of this works but I expect that keeping old node modules around is
bad-idea-jeans.
So, the server starts and the connection works!

But node uses ::1 instead of 127.0.0.1 for `localhost`, which I don't
think puma listens to by default; and I didn't want to fiddle with that.
@zspencer zspencer force-pushed the neighborhood/use-the-latest-lts branch from 18fb3d9 to 4f4f459 Compare October 11, 2023 20:35
@zspencer zspencer merged commit 0d34e50 into main Oct 11, 2023
4 checks passed
@zspencer zspencer deleted the neighborhood/use-the-latest-lts branch October 11, 2023 20:44
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 this pull request may close these issues.

2 participants