Maintenance: offering help with reviews, CI and releases

Hi @dbismut, first of all thanks for use-gesture. @use-gesture/react still gets ~4.9M downloads a week, and it has held up remarkably well since 10.3.1.

On leva (pmndrs/leva#483) you mentioned you were looking for maintainers and that contributions were welcome in the meantime. I'd like to offer the same kind of help here, so rather than just asking, I've started:

• #709: fixes #682. @use-gesture/core's exports only has module and default conditions, so resolvers that don't use module fall through to the CJS builds, and @use-gesture/react re-exports two of them with export *, hence the __esModule conflict. It enables preconstruct's importConditionDefaultExport; module still wins for bundlers that support it, so tree-shaking is unchanged. Verified against the repro from #682, Node ESM/CJS and arethetypeswrong.
• #710: main.yml only runs on push, so no PR from a fork has ever had types, build or tests run by CI. This adds a pull_request trigger; verified on my fork.
• Reviewed #706: tested in Chrome with a real NotFoundError and found the guard leaves the drag stuck active, which blocks later drags; suggested a variant that bails out instead.
• Triaged all 11 open PRs: https://gist.github.com/li1164267803/1032b99733b57ba9c6da1a2c348c076d 4 look ready to merge (docs link fixes, including one pointing at react-spring.io, which now serves an unrelated site, and #687's action updates), 1 duplicate, 1 needs changes, 4 need your call on scope, and #548 is still blocked on the TypeScript issue you were waiting for.
• While doing that I found why transform has no effect on wheel (#692, and the reason #660's reverse couldn't be done with transform): WheelEngine never calls computeValues, so with a custom transform the movement is computed from values that never change. Happy to send a fix.

If it helps, I'd be glad to keep reviewing and help cut releases so fixes like #682 reach users. Starting with triage access only is completely fine.

— Colin