rollbar / rollbar/rollbar-react
All console.logs in Chrome Devtools are swallowed in telemetry.js
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46
- Forks
- 9
- Avg merge
- 2d 56m
- Merged PRs (30d)
- 4
Description
I've implement React Rollbar according to the documentation and the error logs are reaching the dashboard as expected:
import { Provider as ErrorProvider } from '@rollbar/react';
export const rollbarConfig = {
accessToken: import.meta.env.VITE_ROLLBAR_ACCESS_TOKEN,
environment: 'development',
captureUncaught: true,
captureUnhandledRejections: true,
};
// and in the component render wrapping the root app element with...
<ErrorProvider config={rollbarConfig}>
<App />
</ErrorProvider>
The issue is the stack of every console.log in the app now shows it originated at telemetry.js line 518:
day -> 1 telemetry.js:518
Is there a flag to disable this behaviour to see the original source line while developing.
Changing the environment field in the configuration to development did NOT work.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at telemetry.js line 518 and trace how console.log calls are wrapped or intercepted when the React Rollbar provider is configured. Reproduce the behavior in a development React application using the shown configuration, then verify that console logs retain their original source location without breaking error reporting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100