-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ref(wasm): Convert wasm integration to functional integration #10230
Conversation
size-limit report 📦
|
* Process WASM stack traces to support server-side symbolication. | ||
* | ||
* This also hooks the WebAssembly loading browser API so that module | ||
* registrations are intercepted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
while at it, let's deprecate this in favor of the function?
Moving this to browser in v8 makes sense to me, I think. I don't know a whole lot about wasm to be honest, but there is nothing in here which appears overly special 🤔 |
Okay so it can be used in Node as well, but it's not WinterCG so not available in every runtime :/ Maybe let's keep it a separate package for now then, just evaluate this later. |
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.
We should think about moving the wasm integration into
@sentry/browser
and removing@sentry/wasm
all together. What do you think?