-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: unambiguously detect web workers #1728
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1728 +/- ##
=======================================
Coverage 81.03% 81.03%
=======================================
Files 21 21
Lines 1366 1366
Branches 323 323
=======================================
Hits 1107 1107
Misses 182 182
Partials 77 77
☔ View full report in Codecov by Sentry. |
@robertsLando conflicts with #1724 have been resolved, so have the linting issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove the bun.lockdb and pacacke-lock.json changes from the PR
@robertsLando sorry for that. Should be fine now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries! LGTM
Use the same method that
browser-or-node
NPM package uses to detect web workers. This has been tested against my use case for the issue described here, and it works as expected: the Bun runtime is not being (erroneously) identified as a web worker.P.S: Apologies for cancelling the PR initially, but I didn't feel right about it, and I had to run some more tests against my project.