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

JavaScript runtime error: 'BigInt' is not defined #4482

Closed
arindambanerjee1034 opened this issue Feb 14, 2024 · 3 comments
Closed

JavaScript runtime error: 'BigInt' is not defined #4482

arindambanerjee1034 opened this issue Feb 14, 2024 · 3 comments
Labels
bug Something isn't working triage

Comments

@arindambanerjee1034
Copy link

What happened?

Steps to Reproduce

create build with @opentelemetry/exporter-logs-otlp-http
launch on xbox or IE Edge browser.
App crashed with run time error.
JavaScript runtime error: 'BigInt' is not defined

error occurred from https://github.com/open-telemetry/opentelemetry-js/blob/main/experimental/packages/otlp-transformer/src/common/index.ts
L.NO : 21

Expected Result

Should handle run time error.

Actual Result

Additional Details

Unhandled exception

  • JavaScript runtime error: 'BigInt' is not defined
    !*** ../node_modules/@opentelemetry/exporter-logs-otlp-http/node_modules/@opentelemetry/otlp-transformer/build/esm/common/index.js ***!

OpenTelemetry Setup Code

No response

package.json

No response

Relevant log output

Exception was thrown at line 139464, column 5 in ms-appx-web://jjjj.kk/dist/static/js/0.chunk.js
0x800a13b5 - JavaScript runtime error: Assignment to read-only properties is not allowed in strict mode
Unhandled exception at line 30412, column 1 in ms-appx-web://jjjj.kk/dist/static/js/0.chunk.js
0x800a1391 - JavaScript runtime error: 'BigInt' is not defined
!*** ../node_modules/@opentelemetry/exporter-logs-otlp-http/node_modules/@opentelemetry/otlp-transformer/build/esm/common/index.js ***!
@arindambanerjee1034 arindambanerjee1034 added bug Something isn't working triage labels Feb 14, 2024
@pichlermarc
Copy link
Member

Hi @arindambanerjee1034, thanks for reaching out.
Closing this as it looks like it's a duplicate of #4350, if there's reason to believe otherwise, please add a comment here and I'll re-open the issue.

@pichlermarc pichlermarc closed this as not planned Won't fix, can't repro, duplicate, stale Feb 14, 2024
@arindambanerjee1034
Copy link
Author

arindambanerjee1034 commented Feb 14, 2024

Tested with above changes on xbox, build worked fine. Thanks @pichlermarc
Any idea about when we are going to get new package with #4484 change ?

@pichlermarc
Copy link
Member

Tested with above changes on xbox, build worked fine. Thanks @pichlermarc Any idea about when we are going to get new package with #4484 change ?

I think it's safe to assume end of next week, provided #4484 is approved and merged soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
None yet
Development

No branches or pull requests

2 participants