Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#1,114 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
42/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
javascript, nodejs
Bereich
build-system, ci-cd

Rechercherichtung

Reproduziere den Fehler mit der in der Issue beschriebenen package.json- und package-lock.json-Konfiguration und führe dann npm ci mit node-red-node-email ^5.0.2 aus. Vergleiche die Abhängigkeitsmetadaten und das gemeldete Override für utf7 und semver und verwende npm install, um die Lockdatei zu aktualisieren. Die Aufgabe ist abgeschlossen, wenn npm ci erfolgreich ausgeführt wird, ohne ein Override auf Verbraucherseite zu erfordern.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
JavaScript
Sterne
1.1k
Forks
610
Ø Merge
1 T. 4 Std.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus node-red/node-red-nodes

Alle Issues in node-red/node-red-nodes

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.