epsagon / epsagon-browser Goto Github PK

This issue is reproducible if fe use fetch with Request object
Here https://github.com/epsagon/epsagon-browser/blob/main/packages/web/src/instrumentation/fetchInstrumentation.js#L36 we can see that fetch function is called with url and options params: original.apply(this, [url, options]);
But since options is just copy of Request instance, and request instance does not allow to read body property directly, only by calling certain methods link, body property in options variable becomes undefined and fetch call occurs without body
Current behaviour: body for PATCH, POST etc requests is lost
Expected behaviour: body should be send with query

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:

We're using Amplify to submit login credentials to Cognito and we're seeing some errors.

When epsagon web is enabled we see the login request to:
https://cognito-identity.us-west-1.amazonaws.com fail with HTTP 400

In the console we see:
zone.js:372 Uncaught (in promise) SerializationException: SerializationException

We have tried setting:
urlPatternsToIgnore: ['.*cognito-identity.*', '.*cognito-idp.*'],

@epsagon/web: 1.3.1

Edit
This is using the aws-amplify library v4.2.6 and the errors are client side (browser console)

As there is a specific package for React, I don't think the web version should have a dependency on React. This is listed as a peerDependency here

This causes an erroneous warning on install