TD-FE-transpile: add transpilePackages to 8 next.config.ts (RED spec)#127
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
a3ka
pushed a commit
that referenced
this pull request
May 3, 2026
Phase N: scope clean, tests unchanged, 1441/1441 GREEN, landing build EXIT 0. No new tech debt. Ready for architect gate-1 merge.
…* packages Pre-existing infrastructure debt: packages/types/src/index.ts uses .js extension imports (TS NodeNext). Next.js webpack does NOT transpile workspace packages by default — fails to resolve './agent-category.js' (actual file: agent-category.ts). Broke at M-L1-taxonomy merge (commit 120988e, ~April 30). Last successful landing CI: f4cefcf (April 30). Path-filtered landing CI didn't trigger on backend PRs (#118-#125) → silent for 3 days. PR #99 (M-L10.7.3) is first PR touching landing since → CI red → exposes baseline. Affects all 8 frontend apps' production builds + likely silently breaks their Vercel deploys. Acceptance script verifies (17 checks): 1. all 8 apps' next.config.ts have transpilePackages field (8 checks) 2. transpilePackages includes @paxio/types (8 checks) 3. landing-app build succeeds (1 smoke check) Currently RED 0/17 (no transpilePackages in any config; landing-app build fails on .js resolution). Fix is frontend-dev scope — slim spec in docs/sprints/TD-FE-transpile.md.
…ve imports Architect-scope half of TD-FE-transpile fix. With moduleResolution: "bundler" in tsconfig.base.json, .js extensions on relative imports are unnecessary and break Next.js webpack resolution (which can't find ./agent-category.js when actual file is ./agent-category.ts even with transpilePackages). 12 files in packages/types/src/ — strip .js from re-exports and type/value imports. tsc with moduleResolution: "bundler" still resolves correctly. Backend dist/ output (cjs) unaffected — generated .js files already lack runtime .js suffix (resolved at compile time). Pre-existing breakage (commit 120988e M-L1-taxonomy, ~April 30): landing-app build failed because Next.js webpack tried to resolve ./agent-category.js literally. transpilePackages alone (next.config.ts update by frontend-dev) is insufficient — webpack still treats workspace package as ESM and fails on extension mismatch. This commit is the architect half: packages/types/ source rewrite. Frontend-dev's commit covers the next.config.ts additions. NOTE: previous frontend-dev attempt (dfd0195) included these architect-zone changes alongside next.config.ts updates — scope violation per .claude/rules/scope-guard.md::File Ownership (packages/types/ is architect-only). Architect rejected that commit and re-authored the architect half here, preserving frontend-dev's next.config.ts work in the next commit. Verified: pnpm typecheck clean.
Each app's next.config.ts now lists @paxio/{types,ui,hooks,api-client,auth}
in transpilePackages. Tells Next.js webpack to transpile workspace packages
through TS bundler resolution before module resolution.
Combined with architect's previous commit (.js extension strip from
packages/types), this fully fixes the M-L1-taxonomy regression that
broke all 8 frontend apps' production builds since April 30.
17/17 acceptance script PASS, landing-app build succeeds.
(Architect re-applied this commit after frontend-dev's original dfd0195
exceeded scope by also touching packages/types/. This commit isolates
ONLY the next.config.ts portion (frontend-dev scope per scope-guard).
Authorship preserved as frontend-dev@paxio.network.)
a3ka
force-pushed
the
feature/TD-FE-transpile
branch
from
80e3b2f to
14c6465
Compare
a3ka
pushed a commit
that referenced
this pull request
May 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Pre-existing breakage exposed by PR #99:
packages/types/src/index.tsuses.jsextension imports (TS NodeNext convention). Next.js webpack does NOT transpile workspace packages by default — fails to resolve./agent-category.js(actual file:agent-category.ts).Broke at M-L1-taxonomy merge (commit `120988e`, ~April 30). Last successful landing CI: `f4cefcf` (April 30). Path-filtered landing CI didn't trigger on backend PRs (#118-#125) → silent for 3 days. PR #99 first to touch landing since → CI red → exposes baseline.
Affects all 8 frontend apps' production builds + likely Vercel deploys.
What this PR adds
Готово когда
Currently RED
Acceptance script: PASS=0 FAIL=17 (no transpilePackages anywhere; landing build fails). Frontend-dev impl per slim spec → GREEN.
Unblocks
PR #99 (M-L10.7.3) — currently blocked by same issue.
🤖 Generated with Claude Code