I have a node service using express server deployed in production. Internally, it spawns an headless chrome, opens a webpage(developed on react), takes a screenshot of it & returns the screenshot. We are seeing that an issue occurs during rendering of the page causing an exception. We have traced down to the react component where the issue occurs but unable to move forward.
As a last hope, I am trying to see if there is a way to trace back the source(line number in source code maybe?) of failure from the (compiled)application logs using the character number in exception trace logs. They look like as follows,
(Custom-Apollo-Hooks)(] Encountered error) {
errno: 'ECONNRESET',
syscall: 'read',
at /xxxxxx/release_cache/e06cb96d022322dhgs4f5999d4dc5679cf/xx/xx-xxxxxxxx/xxxxxx-service/xxxx/xxxx-server.js:2:57242
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
at Logger$F.error (https://127.0.0.1//v1/js/module/app-aafde331.js:1:49395)
at ps (https://cdn.skypack.dev/-/[email protected]/dist=es2020,mode=imports,min/optimized/react-dom.js:9:9574)
at Ja (https://cdn.skypack.dev/-/[email protected]/dist=es2020,mode=imports,min/optimized/react-dom.js:9:864)
at Tt (https://127.0.0.1//v1/js/module/my-react-component-name.container-52c6ce99.js:1:25073)
I have the compiled JS file, the source code from which it is created. Is there a way to get hints from the character number “57242”(or the ones below) to understand which variable is null, or which line has the issue?
The webpage calls on our graphql APIs to render, hence the apollo hook log, I know the failure is likely related to the API call, here the intent is to map it to the source code as precisely as possible.