NPM Run Configuration: cannot execute some scripts from `package.json`

Open
  • Is something wrong?
#1,899 7 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js
Domain
tooling

Research direction

Start by reproducing the NPM run configuration with the package.json in src/main/webui, using the reported Eclipse and Wild Web Developer versions. Trace how the configured package.json path is resolved and verify that execution uses that path rather than the project root; done when scripts run successfully from the subfolder configuration.

Written by the indexing model from the issue text.

Description

I have a NPM run configuration pointing to an existing package.json (which is not in the root-directory of the project but within a subfolder):

Image

However, executing the run configuration does not work:

npm error code ENOENT
npm error syscall open
npm error path /Users/ev/ide/app/package.json
npm error errno -2
npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/Users/ev/ide/app/package.json'
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: /Users/ev/.npm/_logs/2025-08-03T00_54_31_316Z-debug-0.log

The log says that package.json cannot be found in /Users/ev/ide/app/package.json, although it should look in /Users/ev/ide/app/src/main/webui/package.json as specified in the launch configuration. I also tried with absolute path (= /Users/ev/ide/app/src/main/webui/package.json) in the launch configuration - it shows the same error.

  • On Mac OS
  • Eclipse Version: 2025-03 (4.35.0)
  • Wild Web Developer: 1.3.10.202502071606
Dominant language
Java
Stars
203
Forks
76
Avg merge
1d 5h
Merged PRs (30d)
30

Getting set up

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.

More from eclipse-wildwebdeveloper/wildwebdeveloper

All issues in eclipse-wildwebdeveloper/wildwebdeveloper

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.