-
-
Notifications
You must be signed in to change notification settings - Fork 190
Closed as duplicate of#130
Copy link
Description
Describe the bug
Using the in the. Vue file will cause a debugger abnormal
The following configurations can be used normally
"Vite ": "^1.0.0-rc.13", // version independent
"@ vue/compiler - the SFC" : "^ 3.0.4"
It will cause the debugger position to be abnormal after disposing of the vite.config.js
Such as:
The external import of XXx. HTML is line 100, and the debugger location in the.vue file is line N.
Then the expected debugger position is line 100+N, but the actual debugger position in line N, causing the debugger position to be abnormal
Reproduction
https://github.com/LiuShuZhuang/vite-issues-debugger
System Info
System:
OS: Windows 10 10.0.19043
CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12400F
Memory: 8.36 GB / 15.82 GB
Binaries:
Node: 14.11.0 - d:\Program Files\nodejs\node.EXE
Yarn: 1.22.18 - ~\AppData\Roaming\npm\yarn.CMD
npm: 6.14.8 - d:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.19041.1266.0), Chromium (102.0.1245.44)
Internet Explorer: 11.0.19041.1566
npmPackages:
@vitejs/plugin-vue: ^2.3.3 => 2.3.3
vite: ^2.8.0 => 2.9.12Used Package Manager
npm
Logs
noneValidations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels