Ivan Sanz Carasa

That's the reason, you need to use a `nextBump` in the version policy and it will work as you want it. When no `nextBump` is present it will consider all...

I agree that publishing all the downstream dependencies when the existing semver is still satisfied doesn't sound like the best solution for your use case, but when the version-policy doesn't...

Ah sorry, I misunderstood your issue then, I thought you were using a `lockStepVersion`. The behavior you are experiencing is the "safe" approach for `individualVersion` but I understand the concerns...

hi, im also getting this issue when using jest 29.6.0 and jsdom 22.1.0

For reference, this works on React16 but doesn't on React17/18: ```tsx const Portal = createPortal(children, target) const usage = ```

yeah, as it's marked a direct dependency instead of optional dependency, PNPM warns when using React18 as it's not supported by create-react-context. I think making it an optional dependency could...

TypeScript has definitions to pass a Channel to `throttle` too, but crashes at runtime. Please we need a fix, it's very confusing

Hey @neurosnap thanks, I'm also happy to drop a PR sometime tomorrow if that helps

Hey thanks, I'm also happy to drop a PR sometime tomorrow if that helps

disgusting changes in latest webpack