Skip to content
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

Faro Reported Content Not Processed by Source Map #719

Open
Jeff2Code opened this issue Oct 30, 2024 · 0 comments
Open

Faro Reported Content Not Processed by Source Map #719

Jeff2Code opened this issue Oct 30, 2024 · 0 comments
Assignees

Comments

@Jeff2Code
Copy link

I have a project configured with customize-cra using react-app-rewired, and I’ve enabled source maps. In the production environment, when an error occurs, I can see the corresponding source file location in the browser's console, for example: at t.value (index.jsx:56:11). I integrated the faro-web-sdk to report these errors. However, the reported stacktrace.frames still shows the unprocessed state before source map resolution, for example:

{
  colno: 2047588,
  filename: "some-domain.com/static/js/main.e816bcf6.chunk.js",
  function: "t.value",
  lineno: 1
}

And what i expected maybe was:

{
  colno: 11,
  filename: "index.jsx",
  function: "t.value",
  lineno: 56
}

My current project configuration should already be able to ensure that each error that occurs contains source code information processed by source-map, and then the Faro Web SDK can just report them directly. But it doesn't seem to be the way I thought it would be.

@eskirk eskirk self-assigned this Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants