Skip to content

Comments

docs(config): add vscode debug error tip#19631

Merged
bluwy merged 5 commits intovitejs:mainfrom
btea:docs/add-vscode-debug-config
Mar 14, 2025
Merged

docs(config): add vscode debug error tip#19631
bluwy merged 5 commits intovitejs:mainfrom
btea:docs/add-vscode-debug-config

Conversation

@btea
Copy link
Contributor

@btea btea commented Mar 12, 2025

Description

I saw many people mention related situations in the issue and encountered similar situations during the development process. Therefore, I think it may be more convenient to add relevant situation descriptions to the document.

ref #19110 #19595

Copy link
Contributor

@hi-ogawa hi-ogawa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you 🙏

btea and others added 2 commits March 13, 2025 08:55
Co-authored-by: Hiroshi Ogawa <[email protected]>
Co-authored-by: Hiroshi Ogawa <[email protected]>
hi-ogawa
hi-ogawa previously approved these changes Mar 13, 2025
Copy link
Member

@bluwy bluwy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some suggestions about the wording, but otherwise looks great!

@bluwy bluwy changed the title docs: add vscode debug error situation description docs(config): add vscode debug error tip Mar 14, 2025
@bluwy bluwy merged commit 96ee4f1 into vitejs:main Mar 14, 2025
12 checks passed
@btea btea deleted the docs/add-vscode-debug-config branch March 14, 2025 07:18
moonlitusun pushed a commit to moonlitusun/vite that referenced this pull request May 25, 2025
@nicomouss
Copy link

Thank you @btea and @hi-ogawa !

Could not debug vitest.config.ts properly (always ending up with unbound breakpoints ...). Adding the required configuration in vscode settings.json works very neatly.

Did not see it in the docs, it's kinda hidden deep down the config section, so it's hard to spot.
Landed here instead, so wanted to take a few seconds to thank your both for this contribution !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants