Nev
Nev
> with Redux DevTools enabled, it will result in an error stating "Maximum call stack size exceeded.". However, if you load the project using the "lazyOnload" mode, this issue should...
Semver type definition can't be resolved from @opentelemetry/instrumentation when use rollup bundler
Can you have a look at the opentelemetry-sandbox-web-js as we use rollup to construct bundles for web instrumentations. Here is the rollup configuration that is used their, where we include...
Semver type definition can't be resolved from @opentelemetry/instrumentation when use rollup bundler
Yeah, the sandbox only builds the "browser" bundles (as it's web focused), so we effectively don't use rollup for the node build. Looking at the semver package versions 7.5.2 and...
Semver type definition can't be resolved from @opentelemetry/instrumentation when use rollup bundler
Maybe just adding something like the following to the rollup config to "declare" that it exists??? -- guessing ```json external: ['satisifies'] //
Semver type definition can't be resolved from @opentelemetry/instrumentation when use rollup bundler
> How does your node build work? With rollup it doesn't as we only build the browser packages with it, the main repo uses webpack (for testing) and doesn't actually...
@hectorhdzg , @JacksonWeber can you please look at this
These are (simply) "converted" into regular expressions where any "*" is changed to the `.*` regex (so you can include wildcards). This is done [here](https://github.com/microsoft/ApplicationInsights-JS/blob/65fddb125b16af1b1da0348f0e7eaa3368241f11/shared/AppInsightsCommon/src/Util.ts#L374-L384) This is a simple conversion...
> Does this need to be covered / enforced by the spec? > Different language SDKs already have existing mechanism and they might take different approaches. Agree I don't think...
This is also an issue on the "receiving" server. When a (recent) browser (older ones work differently) sends a sendBeacon request to it "expects" that the receiving server will NOT...
> fetch api with the [keepalive](https://developer.mozilla.org/en-US/docs/Web/API/fetch#keepalive) The fetch with keep-alive flag also has the same 64kb limitation, so if this is payload related it's still going to be an issue...