feat: Add types to config-array

[nzakas]

This adds type checking to the config-array package, generating types for both ESM and CJS.

[eslint-github-bot]

Hi @nzakas!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[kecrily]

We need to either delete the copied dist/{esm,cjs}/types.ts at the end of the build, or rename it to .d.ts when we copy it to avoid generating declarations of statements.

[nzakas]

Sorry, I'm not sure I follow. This outputs both types.ts and types.d.ts in the output directories, unless I'm missing something?

[kecrily]

Yes, types.ts is not required at publish time. And the contents of types.ts and types.d.ts are the same.

[nzakas]

Gotcha. I think we can solve that by using files in package.json to avoid adding another step to this process.

[mdjermanovic]

Gotcha. I think we can solve that by using files in package.json to avoid adding another step to this process.

Should we then do the same in the object-schema package?

[nzakas]

Yes, I'll update all the packages in a separate PR.

[nzakas]

@mdjermanovic would like your review here to get this moving.

[aladdin-add]

LGTM. waiting @kecrily and @mdjermanovic reviewing before merging.

[nzakas]

Looks like packages aren't being properly built in CI, so I created a script to ensure packages are built in the correct order so tsc will be happy.

[kecrily]

Removing prepare script breaks the release workflow. This is because the current workflow does not run build script before NPM publish, but instead relies on installing and executing prepare at the same time. Also JSR publish have a separate build step.

We can remove the prepare scripts for all packages and the JSR publish builds from the workflow, and then add the prepare - build script to the workspace root

---

But I'm sure this can be fixed in another PR

[nzakas]

prepare is not going to work in this repo. I've added a build step to the release workflow to account for that.

[mdjermanovic]

LGTM, thanks!