-
Notifications
You must be signed in to change notification settings - Fork 48.9k
fix: rename bottom stack frame #33680
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
Conversation
a36128f
to
f63d436
Compare
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.
LGTM, cc @sebmarkbage
Comparing: 7216c0f...a8c869c Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: (No significant changes) |
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.
We don't have to check for both in versioned code.
f63d436
to
a8c869c
Compare
`react-stack-bottom-frame` -> `react_stack_bottom_frame`. This survives `@babel/plugin-transform-function-name`, but now frames will be displayed as `at Object.react_stack_bottom_frame (...)` in V8. Checks that were relying on exact function name match were updated to use either `.indexOf()` or `.includes()` For backwards compatibility, both React DevTools and Flight Client will look for both options. I am not so sure about the latter and if React version is locked. DiffTrain build for [91d097b](91d097b)
`react-stack-bottom-frame` -> `react_stack_bottom_frame`. This survives `@babel/plugin-transform-function-name`, but now frames will be displayed as `at Object.react_stack_bottom_frame (...)` in V8. Checks that were relying on exact function name match were updated to use either `.indexOf()` or `.includes()` For backwards compatibility, both React DevTools and Flight Client will look for both options. I am not so sure about the latter and if React version is locked. DiffTrain build for [91d097b](91d097b)
Summary: # Changelog: [Internal] Adaptation for facebook/react#33680. Reviewed By: jackpope Differential Revision: D77737710
Summary: # Changelog: [Internal] Adaptation for facebook/react#33680. Reviewed By: jackpope Differential Revision: D77737710
Summary: Pull Request resolved: #52398 # Changelog: [Internal] Adaptation for facebook/react#33680. Reviewed By: jackpope Differential Revision: D77737710 fbshipit-source-id: 6c6893935e8da8175c0cd9ceab21cc05e2092e7a
Changes from 6.1.3: * feat: static Components panel layout ([hoxyq](https://github.com/hoxyq) in [#33696](#33696)) * fix: support optionality of structured stack trace function name ([hoxyq](https://github.com/hoxyq) in [#33697](#33697)) * fix: rename bottom stack frame ([hoxyq](https://github.com/hoxyq) in [#33680](#33680))
react-stack-bottom-frame
->react_stack_bottom_frame
.This survives
@babel/plugin-transform-function-name
, but now frames will be displayed asat Object.react_stack_bottom_frame (...)
in V8. Checks that were relying on exact function name match were updated to use either.indexOf()
or.includes()
For backwards compatibility, both React DevTools and Flight Client will look for both options. I am not so sure about the latter and if React version is locked.