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

fix: workspace-relative openInEditor paths resolve against cwd and double the package prefix in monorepos

Open
#1,097 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
nuxtjs, typescript

Research direction

Start at the openInEditor entry point described in the issue and inspect how process.cwd(), nuxt.options.workspaceDir, and the existsSync check are used before openInEditorHooks. Reproduce with a pnpm workspace app under apps/web on Windows, then verify that the workspace-relative path opens the expected file and hooks are not blocked by an early failure.

Written by the indexing model from the issue text.

Description

bug
🐛 The bug

In a pnpm monorepo, Component Inspector → Open in Editor fails with a doubled package path:

File not found: <repo>/apps/web/apps/web/app/features/.../SomeComponent.vue

Expected file:

<repo>/apps/web/app/features/.../SomeComponent.vue

(Same pattern for any package under apps/<name>/, e.g. previously apps/app → apps/app/apps/app/....)

Why

openInEditor resolves non-absolute paths with process.cwd() (the Nuxt package root, e.g. apps/web):

if (input.startsWith("./") || !ABSOLUTE_PATH_RE.test(input))
  input = resolve(process.cwd(), input)

The inspector often sends a workspace-relative path like:

apps/web/app/features/.../SomeComponent.vue

So:

cwd (= …/apps/web) + apps/web/app/...  →  …/apps/web/apps/web/app/...

existsSync then fails and returns before openInEditorHooks run, so hooks cannot fix the path.

Nuxt already exposes nuxt.options.workspaceDir for monorepos, but it is not used here.

🛠️ To reproduce

pnpm monorepo with Nuxt at apps/web → pnpm --filter dev (cwd=apps/web) → Component Inspector → Open in Editor → File not found with doubled apps/web/apps/web/...

🌈 Expected behavior

Resolve relative open-in-editor paths against nuxt.options.workspaceDir (and/or try cwd → rootDir → workspaceDir and pick the first path that exists), then open the file.

Ideally openInEditorHooks should also run (or path normalization should happen) before the hard existsSync failure, so consumers can fix monorepo paths.

ℹ️ Additional context
Detailed reproduction
  1. pnpm workspace with Nuxt app at apps/web (not repo root).
  2. Run pnpm --filter <app> dev so process.cwd() is apps/web.
  3. Enable Component Inspector, click a component, Open in Editor.
  4. Observe File not found: …/apps/web/apps/web/app/....

Minimal layout:

repo/
  pnpm-workspace.yaml   # packages: ['apps/*']
  apps/
    web/                # Nuxt app (cwd when running nuxt dev)
      app/
        components/
          Foo.vue
Environment
  • Nuxt: 4.5.x
  • @nuxt/devtools: 3.4.x (via Nuxt)
  • Package manager: pnpm workspace
  • OS: Windows 10/11
Workaround

Local Nuxt module wrapping the DevTools RPC openInEditor to rewrite the path (try cwd / rootDir / workspaceDir + undouble apps/<pkg>/apps/<pkg>/…) before calling the original handler.

Also set:

// nuxt.config.ts
workspaceDir: fileURLToPath(new URL('../..', import.meta.url)), // monorepo root
Related
Dominant language
TypeScript
Stars
3.3k
Forks
214
Avg merge
19h 45m
Merged PRs (30d)
12

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.

More from nuxt/devtools

All issues in nuxt/devtools

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.