···40404141### Browser mode
42424343-To debug [Vitest Browser Mode](/guide/browser/index.md), pass `--inspect` in CLI or define it in your Vitest configuration:
4343+To debug [Vitest Browser Mode](/guide/browser/index.md), pass `--inspect` or `--inspect-brk` in CLI or define it in your Vitest configuration:
44444545::: code-group
4646```bash [CLI]
4747-vitest --inspect --browser
4747+vitest --inspect-brk --browser --no-file-parallelism
4848```
4949```ts [vitest.config.js]
5050import { defineConfig } from 'vitest/config'
51515252export default defineConfig({
5353 test: {
5454- inspect: true,
5454+ inspectBrk: true,
5555+ fileParallelism: false,
5556 browser: {
5657 name: 'chromium',
5758 provider: 'playwright',
···6162```
6263:::
63646464-By default Vitest will use port `9229` as debugging port. You can overwrite it with by passing value in `inspect`:
6565+By default Vitest will use port `9229` as debugging port. You can overwrite it with by passing value in `--inspect-brk`:
65666667```bash
6767-vitest --inspect=127.0.0.1:3000 --browser
6868+vitest --inspect-brk=127.0.0.1:3000 --browser --no-file-parallelism
6869```
69707071Use following [VSCode Compound configuration](https://code.visualstudio.com/docs/editor/debugging#_compound-launch-configurations) for launching Vitest and attaching debugger in the browser:
···7980 "name": "Run Vitest Browser",
8081 "program": "${workspaceRoot}/node_modules/vitest/vitest.mjs",
8182 "console": "integratedTerminal",
8282- "args": ["--inspect", "--browser"]
8383+ "args": ["--inspect-brk", "--browser", "--no-file-parallelism"]
8384 },
8485 {
8586 "type": "chrome",
···120121121122# To run in a single child process
122123vitest --inspect-brk --pool forks --poolOptions.forks.singleFork
124124+125125+# To run in browser mode
126126+vitest --inspect-brk --browser --no-file-parallelism
123127```
124128125129If you are using Vitest 1.1 or higher, you can also just provide `--no-file-parallelism` flag: