lirantal / lirantal/create-node-lib

Bug: scaffolding a new project shows the following error about engines support

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
45
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Bug report

When scaffolding a new project using the CLI:

npx create-node-lib@latest package-name-goes-here
Need to install the following packages:
create-node-lib@2.12.0
Ok to proceed? (y) y

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@semantic-release/github@12.0.6',
npm warn EBADENGINE   required: { node: '^22.14.0 || >= 24.10.0' },
npm warn EBADENGINE   current: { node: 'v24.5.0', npm: '11.5.1' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@semantic-release/npm@13.1.5',
npm warn EBADENGINE   required: { node: '^22.14.0 || >= 24.10.0' },
npm warn EBADENGINE   current: { node: 'v24.5.0', npm: '11.5.1' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: 'semantic-release@25.0.3',
npm warn EBADENGINE   required: { node: '^22.14.0 || >= 24.10.0' },
npm warn EBADENGINE   current: { node: 'v24.5.0', npm: '11.5.1' }
npm warn EBADENGINE }

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with npx create-node-lib@latest package-name-goes-here using the reported Node v24.5.0 and npm 11.5.1 versions. Investigate the scaffolding CLI and its semantic-release dependencies, then verify that creating a project no longer emits the reported EBADENGINE warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.