build: generate types for release

[RebeccaStevens]

PR Checklist

• Addresses an existing open issue: fixes 🚀 Feature: Add types #19
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

Generate types on build:release.

[JoshuaKGoldberg]

Right! Thanks! 🙌

[codecov-commenter]

Codecov Report

Merging #20 (6283ab9) into main (7563431) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #20   +/-   ##
=======================================
  Coverage   25.31%   25.31%           
=======================================
  Files          13       13           
  Lines         237      237           
  Branches       98       98           
=======================================
  Hits           60       60           
  Misses        174      174           
  Partials        3        3           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[JoshuaKGoldberg]

Ah, but the package.json sorting needs to happen. Could you fix the lint issues real quick please?

/home/runner/work/ts-api-tools/ts-api-tools/package.json
Error:   44:4  error  Expected object keys to be in ascending order. 'import' should be before 'types'  jsonc/sort-keys
Error:   54:2  error  Expected object keys to be in ascending order. 'name' should be before 'types'    jsonc/sort-keys

[RebeccaStevens]

One of those linting issue can't be fixed. types must come before any other field in exports.

I don't think sorting package.json fields alphabetically is good idea. We should instead us an approach like in #22

[JoshuaKGoldberg]

types must come before any other field in exports.

...huh, TIL (thanks!). I'll admit I haven't set this up before. Do you have a good resource that describes this?

[RebeccaStevens]

Do you have a good resource that describes this?

Have a look at this: https://www.typescriptlang.org/docs/handbook/esm-node.html#packagejson-exports-imports-and-self-referencing

[JoshuaKGoldberg]

Entry-point for TypeScript resolution - must occur first!

I guess this is blocked on JoshuaKGoldberg/create-typescript-app#223. 😩

[JoshuaKGoldberg]

❤️‍🔥

[JoshuaKGoldberg]

@allcontributors add @RebeccaStevens for bug

[allcontributors]

@JoshuaKGoldberg

I've put up a pull request to add @RebeccaStevens! 🎉

[RebeccaStevens]

Entry-point for TypeScript resolution - must occur first!

I imagine the reason is because when looking for a matching pattern for the path, import is also a valid match as types are imported (require might be to in certain contexts, maybe?). We need to have types first so that types always resolve to types and not JS.