Simen Bekkhus
Simen Bekkhus
>I'd be more ok with it if the type was coming from Jest itself. Definitely. That's still some time out (unless someone else wants to pursue it), so might be...
Don't think so, it'd just look for some other nodes - if they're not there the rule does essentially nothing?
Since Jest now ships its own types, I think adding this rule is fine. It should target types from `@jest/globals` tho, not `@types/jest`. If they overlap, great!
Would you be able to provide a PR @chtpl?
I'd prefer to have CI verify it works with both, but there is no rush at all. It's totally fine to stay on the old version for now
You can use v6 of the plugin already
I like it - happy to take a PR 👍
I think it would be fine to ship types. We already run `tsc`, so it'd just be a quick config change to have it emit definition files. Are we certain...
still getting 500 errors
new error: `Upload failed: {"detail":"Github OIDC Token Auth: Invalid token."}` - weird. I don't understand how they messed up the action so bad 😅