Skip to content

Standardize Node.js setup#179

Merged
desrosj merged 4 commits intomainfrom
standardize-node-setup
Aug 7, 2025
Merged

Standardize Node.js setup#179
desrosj merged 4 commits intomainfrom
standardize-node-setup

Conversation

@desrosj
Copy link
Copy Markdown
Member

@desrosj desrosj commented Jul 22, 2025

Proposed changes

This standardizes the Node.js setup by:

  • Introducing an .nvmrc file specifying the version of Node.js to use when working with the repository.
  • Added engines to the package.json file.

Since 22.x is the current LTS version of Node.js, 22.11.0 is used as the minimum required version since it represents the release that transitioned the version from current to LTS status. The version of npm used (10.9.0) is the version bundled with 22.11.0

This also includes updates to the package-lock.json file that were missed previously. These changes are a result of running npm install before making any other changes in this pull request, but should still be examined and tested carefully.

The GitHub Action workflows have been updated to ensure the desired version is used for testing and releasing, however the release workflow requires newfold-labs/workflows#77 to be merged first.

This addresses PRESS0-2909 and PRESS0-2910.

Type of Change

Production

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Dependency update
  • Refactoring / housekeeping (changes to files not directly related to functionality)

Development

  • Tests
  • Dependency update
  • Environment update / refactoring
  • Documentation Update

Visual

Checklist

  • I have read the CONTRIBUTING doc
  • I have viewed my change in a web-browser
  • Linting and tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

desrosj added 3 commits July 22, 2025 11:37
This standardizes the Node.js setup by:
- Introducing an `.nvmrc` file specifying the version of Node.js to use when working with the repository.
- Added `engines` to the `package.json` file.
@desrosj desrosj self-assigned this Jul 22, 2025
Copilot AI review requested due to automatic review settings July 22, 2025 15:40
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR standardizes the Node.js setup across the repository by establishing Node.js 22.11.0 as the minimum required version, aligning with the current LTS release. The changes ensure consistent Node.js environments for development and CI/CD workflows.

  • Adds Node.js version constraints to package.json and .nvmrc for development environment consistency
  • Updates GitHub Actions workflows to use Node.js 22 for testing and releases
  • Standardizes Node.js version specification across different brand plugin test workflows

Reviewed Changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

File Description
package.json Adds engines field specifying Node.js >=22.11.0 and npm >=10.9.0 requirements
.nvmrc Creates Node Version Manager config file specifying Node.js version 22
.github/workflows/newfold-prep-release.yml Adds node-version parameter set to '22' for release workflow
.github/workflows/brand-plugin-test.yml Updates node-version from 20 to '22' across multiple brand workflows

newfold-labs/workflows#84 will change the default value to `22`.

Once all modules have an `.nvmrc` file, that will be used instead.
@desrosj desrosj merged commit 3e9bfcd into main Aug 7, 2025
9 checks passed
@desrosj desrosj deleted the standardize-node-setup branch August 7, 2025 18:57
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.

3 participants