Preliminary Checks
Reproduction
n/a
Publishable key
n/a
Description
Hi, we saw this error in Sentry for our react app at tldraw.com
TypeError: Cannot read properties of undefined (reading 'captchaHeartbeat')
at eE.isEnabled(/npm/@clerk/clerk-js@5/dist/clerk.browser.js:1:147131)
at eE.start(/npm/@clerk/clerk-js@5/dist/clerk.browser.js:1:146730)
at tf.value(/npm/@clerk/clerk-js@5/dist/clerk.browser.js:1:181517)
at async tf.load(/npm/@clerk/clerk-js@5/dist/clerk.browser.js:1:154285)
at {_IsomorphicClerk#2}.loadClerkJS(../../../../../node_modules/@clerk/clerk-react/dist/index.mjs:1734:9)
With breadcrumbs
Seems like it was immediately preceded by a failure to fetch some json i think?
Expected behavior:
I guess if this was because of the network issue we'd prefer if it were handled gracefully and didn't bubble up to our sentry logs. Or at least it should say something like "network error" so we don't need to report it.
Actual behavior:
An error was thrown.
Environment
System:
OS: macOS 15.1.1
CPU: (10) arm64 Apple M1 Pro
Memory: 84.63 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.11.0 - ~/.nvm/versions/node/v22.11.0/bin/node
Yarn: 4.0.2 - ~/.nvm/versions/node/v22.11.0/bin/yarn
npm: 10.9.0 - ~/.nvm/versions/node/v22.11.0/bin/npm
bun: 1.0.7 - ~/.bun/bin/bun
Browsers:
Chrome: 132.0.6834.111
Safari: 18.1.1
Preliminary Checks
I have reviewed the documentation: https://clerk.com/docs
I have searched for existing issues: https://github.com/clerk/javascript/issues
I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)
This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.
Reproduction
n/a
Publishable key
n/a
Description
Hi, we saw this error in Sentry for our react app at tldraw.com
With breadcrumbs
Seems like it was immediately preceded by a failure to fetch some json i think?
Expected behavior:
I guess if this was because of the network issue we'd prefer if it were handled gracefully and didn't bubble up to our sentry logs. Or at least it should say something like "network error" so we don't need to report it.
Actual behavior:
An error was thrown.
Environment
System: OS: macOS 15.1.1 CPU: (10) arm64 Apple M1 Pro Memory: 84.63 MB / 16.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 22.11.0 - ~/.nvm/versions/node/v22.11.0/bin/node Yarn: 4.0.2 - ~/.nvm/versions/node/v22.11.0/bin/yarn npm: 10.9.0 - ~/.nvm/versions/node/v22.11.0/bin/npm bun: 1.0.7 - ~/.bun/bin/bun Browsers: Chrome: 132.0.6834.111 Safari: 18.1.1