You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then you should be capturing an exception when you load the main page. Unfortunately, this doesn't work - you'll get an error:
TypeError: Sentry2.captureException is not a function
at Index (file:///Users/tmcw/tmp/test-sentry/build/index.js?update=1688751527424:5162:18)
at renderWithHooks (/Users/tmcw/tmp/test-sentry/node_modules/react-dom/cjs/react-dom-server.node.development.js:10:130591)
at renderIndeterminateComponent (/Users/tmcw/tmp/test-sentry/node_modules/react-dom/cjs/react-dom-server.node.development.js:10:132952)
at renderElement (/Users/tmcw/tmp/test-sentry/node_modules/react-dom/cjs/react-dom-server.node.development.js:10:139023)
at renderNodeDestructiveImpl (/Users/tmcw/tmp/test-sentry/node_modules/react-dom/cjs/react-dom-server.node.development.js:10:141963)
at renderNodeDestructive (/Users/tmcw/tmp/test-sentry/node_modules/react-dom/cjs/react-dom-server.node.development.js:10:141404)
at renderIndeterminateComponent (/Users/tmcw/tmp/test-sentry/node_modules/react-dom/cjs/react-dom-server.node.development.js:10:134827)
at renderElement (/Users/tmcw/tmp/test-sentry/node_modules/react-dom/cjs/react-dom-server.node.development.js:10:139023)
at renderNodeDestructiveImpl (/Users/tmcw/tmp/test-sentry/node_modules/react-dom/cjs/react-dom-server.node.development.js:10:141963)
at renderNodeDestructive (/Users/tmcw/tmp/test-sentry/node_modules/react-dom/cjs/react-dom-server.node.development.js:10:141404)
This is kind of a Sentry issue, but I've noticed that @AbhiPrasad is in this repo and I figure this is a perfect minimal testcase for this bug. Afaict, @sentry/remix is correctly resolved to the ESM version of that package, but it relies on @sentry/node and the resolution for @sentry/node is messed up, potentially importing the CJS version of that package and yielding a version of the Sentry object without any of its capturing methods.
On the other hand, though, this is reproducible in just Node and two lines, so I filed an even-more-minimal bug report at getsentry/sentry-javascript#8474 which might be better.
The text was updated successfully, but these errors were encountered:
If you set up a fresh epic-stack instance and then apply this patch:
Then you should be capturing an exception when you load the main page. Unfortunately, this doesn't work - you'll get an error:
This is kind of a Sentry issue, but I've noticed that @AbhiPrasad is in this repo and I figure this is a perfect minimal testcase for this bug. Afaict,
@sentry/remix
is correctly resolved to the ESM version of that package, but it relies on@sentry/node
and the resolution for@sentry/node
is messed up, potentially importing the CJS version of that package and yielding a version of the Sentry object without any of its capturing methods.On the other hand, though, this is reproducible in just Node and two lines, so I filed an even-more-minimal bug report at getsentry/sentry-javascript#8474 which might be better.
The text was updated successfully, but these errors were encountered: