Skip to main content

Fresh Iris App workspaces now type-check and respect your npm release-age policy

Setting up a new Iris App workspace is reliable again: npx @trackunit/create-iris-app-workspace now produces a workspace that passes a type-checked build out of the box, and workspace creation no longer fails with ETARGET if your npm registry enforces a release-age policy (min-release-age or before).

What was broken​

A freshly generated app or UI extension failed tsc with TS5090 (a non-relative path alias) and, for UI extensions, TS6142 (no jsx compiler option). Separately, workspace creation resolved @trackunit/* dependencies against npm's latest, so any developer whose registry enforces a release-age policy hit ETARGET before ever running a build. Nx's CLI usage-data prompt could also stall an otherwise scripted create.

What changed​

  • @trackunit/create-iris-app-workspace (from v2.10.50) installs exact, pinned @trackunit/* versions instead of resolving latest, so it no longer fights a release-age policy, and always passes analytics: false to Nx so the usage-data prompt never appears.
  • @trackunit/iris-app (from v2.16.17) writes ./-relative path aliases for extensions created with extend, and sets jsx in the create template — a fresh workspace now type-checks.
  • @trackunit/migrations (from v0.2.160) adds a v2-16-6-repair-tsconfig migration that applies both of those tsconfig fixes to workspaces created with an older SDK version. Run it with:
npx nx g @trackunit/migrations:migrate
npx nx g @trackunit/migrations:run-migrations

migrate itself (same version) also now resolves @trackunit/* upgrade targets against your npm min-release-age/before policy instead of always picking latest, and fails closed with a clear message when a required version is blocked by that policy.

See Creating a Workspace and Maintaining Your Application for details.