From b78f4d1bba796519073aab4295aede07585bd90f Mon Sep 17 00:00:00 2001
From: Katie Byers <lobsterkatie@gmail.com>
Date: Mon, 11 Apr 2022 17:03:23 -0700
Subject: [PATCH] fix(dev): Fix unit test debugging configuration (#4915)

In https://github.com/getsentry/sentry-javascript/pull/4907, all of our jest config was pulled out of `package.json` and put into `jest.config.js` files. This fixes our VSCode debug profile for unit tests to point to the new config.
---
 .vscode/launch.json | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/.vscode/launch.json b/.vscode/launch.json
index bef12bd786af..2a1d7141b53c 100644
--- a/.vscode/launch.json
+++ b/.vscode/launch.json
@@ -47,9 +47,6 @@
         // this runs one test at a time, rather than running them in parallel (necessary for debugging so that you know
         // you're hitting a single test's breakpoints, in order)
         "--runInBand",
-        // TODO: when we unify jest config, we may need to change this
-        "--config",
-        "${workspaceFolder}/packages/${input:getPackageName}/package.json",
         // coverage messes up the source maps
         "--coverage",
         "false",