Skip to content

Conversation

@clicktodev
Copy link

@clicktodev clicktodev commented Dec 17, 2025

Description

Update package.json to include checks for the required Node.js and npm versions, and revise setup documentation to reflect these prerequisites. This change ensures users have the correct environment for development.

Motivation and Context

How Has This Been Tested?

any attempts to interact with the project throws an error.

example:

> npm install

npm error code EBADDEVENGINES
npm error EBADDEVENGINES The developer of this package has specified the following through devEngines
npm error EBADDEVENGINES Invalid engine "runtime"
npm error EBADDEVENGINES Invalid semver version ">=25" does not match "v24.9.0" for "runtime"
npm error EBADDEVENGINES {
npm error EBADDEVENGINES   current: { name: 'node', version: 'v24.9.0' },
npm error EBADDEVENGINES   required: { name: 'node', version: '>=25' }
npm error EBADDEVENGINES }
npm error A complete log of this run can be found in: /Users/user/.npm/_logs/2025-12-17T11_21_50_617Z-debug-0.log

Screenshots (if appropriate):

Checklist

My PR contains...

  • No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
  • Dependency changes (any modification to dependencies in package.json)
  • Bug fixes (non-breaking change which fixes an issue)
  • Improvements (misc. changes to existing features)
  • Features (non-breaking change which adds functionality)

My changes...

  • are breaking changes to a public API (config options, System API, major UI change, etc).
  • are breaking changes to a private API (Redux, component props, utility functions, etc.).
  • are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
  • are not breaking changes.

Documentation

  • My changes do not require a change to the project documentation.
  • My changes require a change to the project documentation.
  • If yes to above: I have updated the documentation accordingly.

Automated tests

  • My changes can not or do not need to be tested.
  • My changes can and should be tested by unit and/or integration tests.
  • If yes to above: I have added tests to cover my changes.
  • If yes to above: I have taken care to cover edge cases in my tests.
  • All new and existing tests passed.

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.

1 participant