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

Update dependencies and minimum node version requirements #817

Merged
merged 2 commits into from
Aug 1, 2024

Conversation

Neztore
Copy link
Member

@Neztore Neztore commented Jul 31, 2024

At present our package.json supports node v14 which is no longer supported by Node and restricts our abilities to pull in new packages. In this PR I bump our support to v18.18 as this is the minimum version for eslint, and the earliest maintained LTS (in theory we could support earlier minor versions if ignoring eslint, but given this is over a year old and that it will be a new major version, I do not see the need).

Changes made:

  • Bumped minimum supported node version to v18.18
  • Moved all CI/Actions to Node 20 (we've been having warnings about using an old version for a while)
  • Bumped all our dependencies using yarn interactive-update
  • Updated postinstall to use mjs as chalk is no longer a commonjs module in this version
  • migrated to eslint v9

Future work:

  • There is now a native fetch API. We should move to it.

@Neztore Neztore added dependencies Update one or more dependencies version major Increment the major version when merged labels Jul 31, 2024
Copy link
Member

@alanbixby alanbixby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look visually OK.

@Neztore Neztore merged commit 67d3570 into master Aug 1, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Update one or more dependencies version major Increment the major version when merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants