Update react-devtools-inline to 4.18.0 to fix node_modules size

[markerikson]

Ref: facebook/react#22220

4.17.0 was a known bad release with an unzipped size of 400MB+. 4.18 only has a couple changes, and it's still before the React DevTools "protocol bridge" version changed in 4.22.0:

• https://github.com/facebook/react/blob/main/packages/react-devtools/CHANGELOG.md#4220

So, bumping this to use 4.18 as our "old protocol bridge version" package should still be safe, and shrink the install size we need locally.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
devtools	✅ Ready (Inspect)	Visit Preview	Oct 12, 2022 at 8:54PM (UTC)

[qa-wolf]

✅ QA Wolf - Deploy PR

Chewy here: 8 tests ran, see details here.

✅ 8 passed

• ✅ User role unable to: access billing, view api keys, delete team, edit team name

• ✅ Share replay via invite link: only people with access

• ✅ View footer links: about

• ✅ Log in and out

• ✅ View and search library

• ✅ View and click events

• ✅ Share replay via invite link: members of Test team

• ✅ Share replay via invite link: members of QAWolf :: Facebook

[replay-io]

48 replays were recorded for cd05d2e.

3 Failed

• inspector-02: element picker and iframe behavior
• inspector-04: Test that styles for elements can be viewed
• logpoints-04: should display exceptions in the console

45 Passed

• breakpoints-01: Test basic breakpoint functionality
• breakpoints-02: Test unhandled divergence while evaluating at a breakpoint
• breakpoints-03: Test stepping forward through breakpoints when rewound before the first one
• breakpoints-04: catch, finally, generators, and async/await
• breakpoints-05: Test interaction of breakpoints with debugger statements
• breakpoints-06: Test log point in a sourcemapped file
• breakpoints-07: rewind and seek using command bar and console messages
• console_async: support global console evaluations in async frames
• console_errors: Test that errors and warnings from various sources are shown in the console
• console_eval: support global console evaluations
• console_warp-01: should support warping to console messages
• console_warp-02: support pausing, warping, stepping and evaluating console messages
• focus_mode-01: should filter messages as regions based on the active focus mode
• highlighter: element highlighter works everywhere
• inspector-01: Test that scopes are rerendered
• inspector-03: Test that styles for elements can be viewed
• inspector-05: Test that styles for elements can be viewed
• inspector-06: Test that styles for elements can be viewed
• inspector-07: Test that styles for elements can be viewed
• logpoints-01: log-points appear in the correct order and allow time warping
• logpoints-02: conditional log-points
• logpoints-03: should display event properties in the console
• node_console-01: Basic node console behavior
• node_console-02: uncaught exceptions should show up
• node_control_flow: catch, finally, generators, and async/await
• node_logpoint-01: Basic node logpoints
• node_logpoint-02: Node exception logpoints
• node_object_preview: Showing console objects in node
• node_spawn: Basic subprocess spawning
• node_stepping-01: Test stepping in async frames and async call stacks
• node_worker-01: make sure node workers don't cause crashes
• object_preview-01: expressions in the console after time warping
• object_preview-02: should allow objects in scope to be inspected
• object_preview-03: Test previews when switching between frames and stepping
• object_preview-04: Test scope mapping and switching between generated/original sources
• react_devtools: Test React DevTools.
• repaint: repaints the screen screen when stepping over code that modifies the DOM
• scopes_rerender: Test that scopes are rerendered
• sourcemap_stacktrace: Test that stacktraces are sourcemapped
• stacking: Element highlighter selects the correct element when they overlap
• stepping-01: Test basic step-over/back functionality
• stepping-02: Test fixes for some simple stepping bugs
• stepping-03: Stepping past the beginning or end of a frame should act like a step-out
• stepping-05: Test stepping in pretty-printed code
• stepping-06: Test stepping in async frames and async call stacks

View test run on Replay ↗︎