-
Notifications
You must be signed in to change notification settings - Fork 261
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
Avoid embedding web-worker polyfill #12400
base: master
Are you sure you want to change the base?
Conversation
The BLOB code from web-worker is minified, and contains source maps that are then passed over by webpack - that creates a situation of minified code inside BLOB inside minified code which confuses some tools, eg. jantimon/chrome-profile-sourcemap-resolver#4 That could be fixed, but the only reason to do so would be supporting very old (pre-2013) browsers, so we are better off removing the polyfill altogether. Signed-off-by: Silvio Moioli <silvio@moioli.net>
End-to-end failures seem unrelated to me, but please advise if they are not. |
Fallback came in via #6563 |
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.
Think this is ok, but would like to confirm a prod build running remotely works (given #6563). Just making one now (richard-dev
).
If that's fine then we just need to wait for 2.10 branching (happening right now)
Summary
Fixes: #12511
TL;DR: Drop the web-worker polyfill. It's for ancient browsers and confuses tooling that works with performance captures.
QA NOTE: No user visible change expected, this is only to aid developers interpreting performance captures, eg. following https://github.com/rancherlabs/rancher-process/blob/main/docs/documentation/howtos/browser_performance_capture.md
Technical notes summary
The BLOB code from web-worker is minified, and contains source maps that are then passed over by webpack - that creates a situation of minified code inside BLOB inside minified code which confuses some tools, eg.
jantimon/chrome-profile-sourcemap-resolver#4
That could be fixed, but the only reason to do so would be supporting very old (pre-2013) browsers, so we are better off removing the polyfill altogether.
Areas or cases that should be tested
Nothing in particular, exisiting tests should abundantly cover this.
Areas which could experience regressions
None expected.
Checklist