Miles Johnson

@chinesedfan Have you tried `yarn upgrade-interactive`?

Why not yarn install the transitive dep you want to update but don't commit the package.json changes, just the yarn.lock?

@djmitche Right. You would need to install the version within the range expected. Not ideal and a bit tedious, but an available stopgap for now.

This also causes `DEBUG` to be useless with NPM scripts, for example `DEBUG=beemo:* `. > No matches found: "beemo:*" Furthermore, is it possible to escape it? I have `--workspaces=*` which...

I think something else is happening in relation to Yarn 2. My scripts hang on windows until they timeout, but according to the debugs, they ran fine. But that's a...

I agree with @ti1024. More and more packages are providing native binaries (Rust, Go), and not having these work via Yarn is a huge problem IMO. What if yarn inspected...

@pcjmfranken Corepack doesn't require npm. It's built into Node.js as of v14.19, which everyone should be using since v12 is EOL in a few days.

@ecozoic I'm having the exact same problem. Did you ever figure it out? `StyleSheetTestUtils.suppressStyleInjection` doesn't actually fix the problem for me.

I've dug into this a bit and I believe the issue is race conditions. Here's the act code and the block where the console log happens: https://github.com/facebook/react/blob/master/packages/react-reconciler/src/ReactFiberWorkLoop.old.js#L3680 You'll notice this...

@ryanhobsonsmith By default `fireEvent` wraps in `act` and the handler being fired **must** be _synchronous_, but because of `setTimeout`, that `onPress` is technically _asynchronous_. So in your example above, the...