Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

NPM CI fails when node-red-node-email-5.0.2 is present in package.json

Aperta
  • Qualcosa non va?
#1,114 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
javascript, nodejs
Ambito
build-system, ci-cd

Direzione di ricerca

Riproduci il malfunzionamento utilizzando la configurazione di package.json e package-lock.json descritta nell’issue, quindi esegui npm ci con node-red-node-email ^5.0.2. Confronta i metadati delle dipendenze e l’override segnalato per utf7 e semver, utilizzando npm install per aggiornare il lockfile. Il lavoro è completato quando npm ci viene eseguito correttamente senza richiedere un override lato consumer.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

upstream
Which node are you reporting and issue on?

node-red-node-email

What are the steps to reproduce?

The first step is to install the package in the latest version.

 npm i node-red-node-email

added 1 package in 883ms

12 packages are looking for funding
  run `npm fund` for details
npm notice
npm notice New minor version of npm available! 11.6.2 -> 11.7.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.7.0
npm notice To update run: npm install -g [email protected]
npm notice

Then, check if the package was successfully installed.

 $ cat package.json 
{
  "dependencies": {
    "node-red-node-email": "^5.0.2"
  }
}

Run npm ci to see the errors:

 $ npm ci
npm error code EUSAGE
npm error
npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm error
npm error Missing: [email protected] from lock file
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm error [--no-bin-links] [--no-fund] [--dry-run]
npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm error [--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error aliases: clean-install, ic, install-clean, isntall-clean
npm error
npm error Run "npm help ci" for more info
npm error A complete log of this run can be found in: /home/rebeca/.npm/_logs/2025-12-11T13_19_47_559Z-debug-0.log

Workaround

To fix the error in my case, I added the following override rule in the package.json:

 {
   "dependencies": {
     "node-red-node-email": "^5.0.2"
+  },
+  "overrides": {
+    "utf7": {
+      "semver": "^5.7.2"
+    }
   }
 }

And update the package-lock.json:

npm install

added 1 package, and audited 44 packages in 2s

12 packages are looking for funding
  run `npm fund` for details

4 low severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Now it's possible to run the npm ci with no problem

npm ci

added 1 package, and audited 44 packages in 943ms

12 packages are looking for funding
  run `npm fund` for details

4 low severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force
What happens?

Run npm ci to see the errors:

 $ npm ci
npm error code EUSAGE
npm error
npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm error
npm error Missing: [email protected] from lock file
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm error [--no-bin-links] [--no-fund] [--dry-run]
npm error [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm error [--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error aliases: clean-install, ic, install-clean, isntall-clean
npm error
npm error Run "npm help ci" for more info
npm error A complete log of this run can be found in: /home/rebeca/.npm/_logs/2025-12-11T13_19_47_559Z-debug-0.log
What did you expect to happen?

To install the package using npm ci without problems.

Example flow

No response

Environment
  • Node-RED version: 4.x
  • Node.js version: 24.12.0
  • npm version: 11.6.2
  • Platform/OS: Linux Mint 22.1
Lingua principale
JavaScript
Stelle
1.1k
Fork
610
Merge medio
1g 4h
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di node-red/node-red-nodes

Tutte le issue di node-red/node-red-nodes

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.