Jake Bailey

Note that there's also a popular grouper, eslint-plugin-simple-import-order, which is also widely used and does things differently. Personally, I don't think that trying to implement all of the options is...

FWIW my opinion here changed a bit having dealt with using ESLint on TS itself now that we're modules; using dprint to group would be a lot faster and less...

I would be hoping for something as powerful as: https://github.com/lydell/eslint-plugin-simple-import-sort/#custom-grouping The way that the sorting works is kind of odd, in that it uses only regexes, then a special unicode...

Related, but pnpm has also started having sporadic problems that only happen on this new image version, and it's breaking DefinitelyTyped: https://github.com/DefinitelyTyped/DefinitelyTyped/actions/runs/8587816469/job/23531927867?pr=69212

This also broke TypeScript's nightly publish: https://github.com/microsoft/TypeScript/actions/runs/8586934300/job/23529969314

Reran a few times and got the old image again; it passed on the old image: https://github.com/jakebailey/hereby/actions/runs/8585240094/job/23532442215 But another rerun failed on the new one: https://github.com/jakebailey/hereby/actions/runs/8585240094/job/23532442281 This seems to be...

All in all, though, I don't understand why the image update broke things; in all of these cases the install came after setup-node, so why is npm even 10.x on...

I think I see a pattern; on the latest runner image, if setup-node runs without check-latest, the globally installed node is used and a global install of npm fails. For...

I did a bunch of testing, and the particular bad situation is: - When using `setup-node` and _not_ specifying a version, it doesn't do anything, leaving the global node/npm on...

This was fixed in #51300, yes.