Skip to content
This repository has been archived by the owner on Jun 13, 2023. It is now read-only.

Using Epsagon with typescript projects and enabling source maps #101

Open
Metagrids opened this issue Sep 6, 2022 · 0 comments
Open

Using Epsagon with typescript projects and enabling source maps #101

Metagrids opened this issue Sep 6, 2022 · 0 comments

Comments

@Metagrids
Copy link

Hi Epsagon team, I am opening this issue to get your advice on using Epsagon with Typesscript React projects created via CRA.
There are several problems with my current setup:

  1. during project startup, we see a lot of errors without any reason. They are not blocking the build but makes the build logs on AWS very noisy and hard to read.
  2. When an exception happens, the errors doesn't refer to the source code (Typescript) instead they only indicate the main javascript bundle. Enables source maps on tsconfig did not solve the issue.

Could you please point me to a document that explains how to setup CRA Typescript projects? An example project will also be very useful.

Example of errors:

2022-09-06T14:30:52.786+01:00CopyFailed to parse source map from '/codebuild/output/src751190034/src/github.com///node_modules/@opentelemetry/api/src/internal/semver.ts' file: Error: ENOENT: no such file or directory, open '/codebuild/output/src751190034/src/github.com///node_modules/@opentelemetry/api/src/internal/semver.ts' Failed to parse source map from '/codebuild/output/src751190034/src/github.com///node_modules/@opentelemetry/api/src/internal/semver.ts' file: Error: ENOENT: no such file or directory, open '/codebuild/output/src751190034/src/github.com///node_modules/@opentelemetry/api/src/internal/semver.ts'
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant