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

Chore: Upgrade Node to v22, update deps #242

Merged
merged 6 commits into from
Aug 29, 2024
Merged

Chore: Upgrade Node to v22, update deps #242

merged 6 commits into from
Aug 29, 2024

Conversation

drwpow
Copy link
Contributor

@drwpow drwpow commented Aug 16, 2024

Changes

  • Updates Node from 1622. Node 16 is EOL. Welcome to the future 😎
  • Updates deps. Because there were install errors for old packages on modern Node versions, and also because there were multiple security warnings.
  • Updates GitHub Actions to current versions.

Reviewing

@drwpow drwpow requested a review from kaelig August 16, 2024 21:46
Copy link

netlify bot commented Aug 16, 2024

Deploy Preview for dtcg-tr ready!

Name Link
🔨 Latest commit 2777c5a
🔍 Latest deploy log https://app.netlify.com/sites/dtcg-tr/deploys/66cebc76bc02a80008730786
😎 Deploy Preview https://deploy-preview-242--dtcg-tr.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@drwpow drwpow mentioned this pull request Aug 16, 2024
@drwpow drwpow changed the title Upgrade Node to v22 Upgrade Node to v22, update deps Aug 16, 2024
with:
path: ~/.npm
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-
- uses: actions/setup-node@v3
with: { node-version: 16, cache: npm }
Copy link
Contributor Author

@drwpow drwpow Aug 16, 2024

Choose a reason for hiding this comment

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

These days it’s generally safe to omit the Node version. Not only do major versions not break as often for most users anymore (unless you’re using bleeding-edge/experimental features), GitHub Actions also is pretty slow/cautious in changing the default. They’ll only use stable versions (even numbers in Node’s numbering system), and they’ll always wait several patches to make sure it’s safe.

Just using the latest Node version is not only more secure; it also tends to get faster with V8 updates.

@drwpow drwpow changed the title Upgrade Node to v22, update deps Chore: Upgrade Node to v22, update deps Aug 16, 2024
@kaelig
Copy link
Member

kaelig commented Aug 22, 2024

I just updated the Netlify Site configuration to use Node v20. Node v22 should work too, but isn't fully supported.

@kaelig
Copy link
Member

kaelig commented Aug 22, 2024

Looks like Chrome isn't available anymore – can you look into it?

@drwpow
Copy link
Contributor Author

drwpow commented Aug 22, 2024

Looks like Chrome isn't available anymore – can you look into it?

Sorry; what do you mean by Chrome not being available?

@kaelig
Copy link
Member

kaelig commented Aug 23, 2024

Chrome must have been available in the old build image (see error logs), and isn't available with the Node 22 build image. I believe it's necessary for ReSpec to build.

@drwpow
Copy link
Contributor Author

drwpow commented Aug 28, 2024

Chrome must have been available in the old build image (see error logs), and isn't available with the Node 22 build image. I believe it's necessary for ReSpec to build.

Just added a setup step for Puppeteer in Netlify. I think Netlify caches this well as it was pretty instant.

@@ -1,4 +1,4 @@
<!DOCTYPE html>
<!doctype html>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Just Prettier autoformatting in latest version

@drwpow
Copy link
Contributor Author

drwpow commented Aug 28, 2024

I just updated the Netlify Site configuration to use Node v20. Node v22 should work too, but isn't fully supported.

Also that’s fine! Node v20 is fine. I only updated to v22 because it’s been out for a while, it’s the latest stable version, and will be replacing v20 as the new active version in only a couple months. But it’s all fine, as long as we’re upgraded off an EOL version 😅

@kaelig kaelig merged commit 729cbd8 into main Aug 29, 2024
6 checks passed
@kaelig kaelig deleted the drwpow/upgrade-node branch August 29, 2024 18:12
github-actions bot added a commit that referenced this pull request Aug 29, 2024
SHA: 729cbd8
Reason: push, by kaelig

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot added a commit that referenced this pull request Aug 29, 2024
SHA: 729cbd8
Reason: push, by kaelig

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot added a commit that referenced this pull request Aug 29, 2024
SHA: 729cbd8
Reason: push, by kaelig

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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