fix(postgrest-typegen): order generated output with a fixed collation

[spydon]

Stacked on #180 (which is stacked on #179).

Summary

sortGeneratorMetadata, the TypeScript generator's merge sorts and the Swift generator's sorts all used String.prototype.localeCompare without a locale, so the canonical order of generated output depended on the default locale of the machine running the generator.

Reproduction with Node 26:

LANG=en_US.UTF-8 node -e '...["b","ä","a","z"].sort((a,b)=>a.localeCompare(b))'   # ["a","ä","b","z"]
LANG=sv_SE.UTF-8 node -e '...'                                                      # ["a","b","z","ä"]

Bun currently ignores the host locale and always resolves en-US, so the CLI binary is not affected today, but postgres-meta and any Node consumer are, and nothing pins the behaviour.

All 24 comparisons now go through a single Intl.Collator("en") in src/collation.ts. English has no tailoring over the ICU root collation, so this is exactly the order the English CI runners and the postgres-meta parity fixtures already produce; only machines with another default locale change, and they now agree with CI.

Verification

• New test in sort.test.ts asserting ["a", "ä", "b", "z"] regardless of host locale.
• bun run test with Docker: 134 pass. No snapshot or parity fixture changed, which is the point.
• check-types, format-and-lint and knip pass.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: d569d106-4ac0-4797-a374-be942e7d2b64

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}