Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error: Running command error

Open
#114 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, nuxt, typescript
Domain
devtools, web-dev

Research direction

The payload names no source file or test. Start by running pnpx node-modules-inspector on Windows 11 with pnpm and reproduce the 500, then trace the failed _nuxt/chunks/default.ChfS6AKT.js dynamic import in the Nuxt app; done means the command starts without the error.

Written by the indexing model from the issue text.

Description

Describe the bug

500
Failed to fetch dynamically imported module: http://localhost:9999/_nuxt/chunks/default.ChfS6AKT.js

Image

Reproduction

pnpx node-modules-inspector

System Info
System:
    OS: Windows 11 10.0.26100
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-1235U
    Memory: 3.90 GB / 15.68 GB
  Binaries:
    Node: 24.2.0 - ~\AppData\Local\Volta\tools\image\node\24.2.0\node.EXE
    Yarn: 1.22.22 - ~\AppData\Local\Volta\tools\image\yarn\1.22.22\bin\yarn.CMD
    npm: 11.3.0 - ~\AppData\Local\Volta\tools\image\node\24.2.0\npm.CMD
    pnpm: Active code page: 65001
9.15.0 - ~\AppData\Local\Volta\bin\pnpm.CMD
  Browsers:
    Edge: Chromium (135.0.3179.73)
    Internet Explorer: 11.0.26100.1882
Used Package Manager

pnpm

Validations
  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.
Contributions
  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
Dominant language
TypeScript
Stars
3k
Forks
92
Avg merge
3h 49m
Merged PRs (30d)
4

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 antfu/node-modules-inspector

All issues in antfu/node-modules-inspector

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.