Noah Allen

Fair enough! I'll test once the other fix is on npm.

@Andarist, I think this might help with #366 as well. Would love to see a fix! :)

I tend to agree with @kkmuffme, but I do think this would be a breaking change for `@wordpress/scripts`, so I didn't want to merge that without more feedback :)

I believe this was changed in this PR: https://github.com/WordPress/gutenberg/pull/45005/files#diff-b20e58387aaaf1809d52371285cc4ac37a5d860ab462647f038cbdaf54e9b876L81 cc @talldan @jameskoster @aaronrobertshaw for feedback on this one

> It's a valid point that if dotcom is having issues because they are auto-enabling, and updating, the Gutenberg plugin on every site, it may be time to stop doing...

This might be blocked by Gutenberg changes, since we rely on the WP stylelint config. More context: - https://github.com/WordPress/gutenberg/pull/51192 - https://github.com/WordPress/gutenberg/pull/50336 - https://github.com/WordPress/gutenberg/pull/48143

@brunolemos I was trying to run debug from Android Studio as well! The `onPause` fixed it for me. I think it was because there's a point where the app shows...

I opened a related issue in the DT repo, for reference: https://github.com/DefinitelyTyped/DefinitelyTyped/discussions/65890. Unfortunately, the types as they exist aren't strong enough to prevent crashes.

Looks like it is simply impossible to catch this type of issue with TS, which is suuuper unfortunate. Honestly, I really wish that React _didn't_ crash here. IMO, it's unlikely...

I'm guessing this is blocked until webpack 5 is supported in storybook core? There are some improvements in `sass-loader` v11 we'd like to use :)