Vue DevTools(Chrome) Not Recognizing Base Path in Vite Project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 279
- PR merge metrics
- No merged PRs in 30d
Description
Description:
I am working on a project with a monorepo structure, and I'm using Vite for development. My project is configured with a base path of /data-panel/ in Vite, which works fine for the application itself. However, when I try to use Vue DevTools Chrome Extension, it seems not recognize the base path (/data-panel/), and the paths for assets and Vue components are incorrect, leading to errors.
network response: The server is configured with a public base URL of /data-panel/ - did you mean to visit /data-panel/__open-in-editor?file=C:/Users/Administrator/Desktop/business/data-panel-front/data-panel/src/components/business/mobile/BusinessIndexCardMobileV2.vue instead?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Vue DevTools Chrome Extension issue in a monorepo Vite project configured with the /data-panel/ base path, then inspect the network requests for assets, component paths, and __open-in-editor. Done means these paths consistently include the configured base path and no longer produce the public-base-URL error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vite
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100