Add typescript project references

[JakeLane]

Motivation

• Excessive use of type suppressions reduces type safety.

• Insufficient type coverage, especially in tests or areas lacking check-ts.

• Inconsistent test checking, with check-ts not functioning reliably across all environments.

Changes

Moving to typescript project references, which is the modern way to handle monorepos. This should improve reliablity and give us a single command for building/checking ts (yarn build:ts).

Also adding a type coverage command and comment to gamify the improvement of types.

Checklist

• Existing or new tests cover this change
• There is a changeset for this change, or one is not required
• Added documentation for any new features to the docs/ folder

[changeset-bot]

⚠️ No Changeset found

Latest commit: 80b653a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

📊 Type Coverage Report

Overall Coverage

Metric	Value
Coverage Percentage	NaN%
Correctly Typed	0
Total Expressions	0
Untyped Expressions	0
Status	✅ Success

Note: No baseline data available to compare with.

---

This report was generated by the Type Coverage GitHub Action

[ferris-atlaspack-bot]

🦀 Ferris' Rust Changeset Check

Ferris says: Hi! I noticed you changed some .rs files but you didn't bump the Rust package.

If you want your Rust changes published, you will need to bump the @atlaspack/rust package in your changeset.

[marcins]

Neat! What's the workflow when you modify dependencies in a package? Do you re-run the scripts/update-ts-references.mjs script? I guess CI will error if you don't (or is it fast enough to do in pre-commit?)

[JakeLane]

Neat! What's the workflow when you modify dependencies in a package? Do you re-run the scripts/update-ts-references.mjs script? I guess CI will error if you don't (or is it fast enough to do in pre-commit?)

Just running yarn build:ts should be enough. I chucked it straight in the build script because it's pretty fast