From 7e3207de0634a00d458a4249d6b69542d5583c03 Mon Sep 17 00:00:00 2001
From: Lukas Stracke <lukas.stracke@sentry.io>
Date: Mon, 22 Jan 2024 14:19:08 +0100
Subject: [PATCH] fix(wasm): Add `@sentry/core` as a dependency (#10283)

By using functional integrations in #10230, we started importing from
`@sentry/core` in the WASM integration. However, we didn't register
`@sentry/core` as a dependency, making rollup bundle core into the
package output. This changed the `build/npm` directory structure, making
our entry points in `package.json` invalid.

This PR fixes things by simply registering core as a dependency of wasm.
If we move WASM to core (which I strongly think we should do), we'll be
able to get rid of this again.
---
 .github/workflows/build.yml | 1 +
 packages/wasm/package.json  | 3 ++-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 088a5b19404b..d66831462844 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -102,6 +102,7 @@ jobs:
               - 'packages/replay/**'
               - 'packages/replay-canvas/**'
               - 'packages/feedback/**'
+              - 'packages/wasm/**'
             browser_integration:
               - *shared
               - *browser
diff --git a/packages/wasm/package.json b/packages/wasm/package.json
index 899141b4f6a7..6cea967b1583 100644
--- a/packages/wasm/package.json
+++ b/packages/wasm/package.json
@@ -31,7 +31,8 @@
   "dependencies": {
     "@sentry/browser": "7.94.1",
     "@sentry/types": "7.94.1",
-    "@sentry/utils": "7.94.1"
+    "@sentry/utils": "7.94.1",
+    "@sentry/core": "7.94.1"
   },
   "scripts": {
     "build": "run-p build:transpile build:bundle build:types",