npm / npm/cli

NPM v9.5.1 on Node.js v18.16.0 in AIX 7.2 TL5 the npm stop is not triggering

Open
#6,602 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Needs Triage Release 9.x
Dominant language
JavaScript
Stars
10.1k
Forks
4.7k
Avg merge
2d 2h
Merged PRs (30d)
19

Description

Is there an existing issue for this?
  • I have searched the existing issues
This issue exists in the latest npm version
  • I am using the latest npm
Current Behavior

I am facing the Issue that when we trigger the "npm stop" from Script file it getting an error node --expose_gc ./lib/stop.js: --: not found The Node version I am using is v18.16.0, NPM version v8.17.0 and upper version

And also I am facing issue with node v18.16.0, NPM version v9.5.1 the npm start is triggering from script file but npm stop is not triggering. This node version of 18.16.0, I am working on Linux system with AIX 7.2. We have tried downgrade the npm version to v8.11.0 it working. Till npm v8.16 it working as accepted but after npm v8.17.0 facing error node --expose_gc ./lib/stop.js: --: not found

Expected Behavior

I have tried to downgrade the NPM version it working

Steps To Reproduce

when I tried to trigger the npm stop from the script file. npm stop is not working. The environment I am using is Node 18.16.0 with NPM version 9.5.1 in OS AIX 7.2

Environment

npm -v: npm 9.5.1
node -v: Node.js: 18.16.0
system: AIX 7.2
npm stop is not triggering from script file

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

Reproduce the npm stop failure on AIX 7.2 with Node.js 18.16.0 and npm 9.5.1, comparing npm 8.16 with 8.17. Inspect the reported lib/stop.js invocation and the script-file trigger; done means npm stop runs successfully without the “--: not found” error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.