-
-
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
Latest @sentry/browser asks for node types #2927
Labels
Comments
MhMadHamster
changed the title
Latest @sentry/browser asks fore node types
Latest @sentry/browser asks for node types
Sep 30, 2020
9 tasks
Not sure if related, but installing
|
Yep, caused by this commit: Importing "domain" (part of the node stdlib) puts all of node into the ambient context and breaks everyone's browser projects. This is a very persistent issue with libs that support both node and the browser: |
aleclarson
added a commit
to aleclarson/sentry-javascript
that referenced
this issue
Nov 13, 2020
2 tasks
See #3050 for a fix. |
HazAT
added a commit
that referenced
this issue
Nov 13, 2020
* fix: stop using @types/node in @sentry/hub Fixes #2927 * fix: Linter Co-authored-by: Daniel Griesser <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Package + Version
@sentry/browser
@sentry/node
raven-js
raven-node
(raven for node)Version:
Description
Latest version of
@sentry/browser
via dependencies pulls@sentry/hub
which requires node types, essentially making@sentry/browser
dependent on node types, and that makes little sense to me since i'm using it in browser. For me the culprit isnode_modules\@sentry\hub\dist\interfaces.d.ts
asking for "domain" module from node types.The text was updated successfully, but these errors were encountered: