fix(utils): drop the .js specifiers Turbopack cannot resolve

[waleedlatif1]

Summary

Staging is currently broken for every developer running the app locally. Any route whose module graph reaches the @sim/utils barrel returns 500 under next dev:

Module not found: Can't resolve './errors.js'
> 1 | export { getErrorMessage, getPostgresErrorCode, toError } from './errors.js'

Import trace:
  ./packages/utils/src/index.ts
  ./apps/sim/lib/embeddings/client.ts
  ./apps/sim/lib/knowledge/embeddings.ts
  ./apps/sim/app/api/knowledge/route.ts

packages/utils/src/index.ts addresses its siblings as ./errors.js while the files are ./errors.ts. webpack rewrites that via resolve.extensionAlias; Turbopack has no equivalent — vercel/next.js#82945.

next build is webpack. next dev is Turbopack. So this shape passes CI and breaks every dev server — which is exactly what happened: #6317's CI was fully green.

Nothing required the extensions. The repo is on moduleResolution: "bundler" and no other package barrel uses them.

Changes

Two fixes, either of which resolves the symptom. Both are here because they fail differently:

1. packages/utils/src/index.ts — drops all 12 .js specifiers. Fixes the barrel for every current and future consumer.

2. apps/sim/lib/embeddings/client.ts — imports chunkArray from @sim/utils/helpers instead of the barrel. feat(embeddings): multi-provider Embeddings block on a shared core #6317 added the only bare-barrel @sim/utils import in the monorepo; the subpath form is the documented convention (CLAUDE.md, "Common Utilities") and resolves to one module instead of pulling twelve.

3. scripts/check-import-specifiers.ts (new, wired into CI) — fails the build on either shape.

Type of Change

• Bug fix

Testing

Verified against a real bun run dev:full with production env vars:

Route	before	after
GET /api/knowledge	500	401
POST /api/tools/embeddings	500	401
POST /api/workflows/[id]/deploy	500	401
GET /workspace	200 (chrome only)	200

• Turbopack log free of Module not found after the fix
• bunx tsc --noEmit — 0 errors
• packages/utils — 147/147 tests pass
• apps/realtime boots normally (it consumes @sim/utils under Bun, unaffected either way)

The guard was verified to fail, not just to pass — restoring both halves of the bug produces:

✗ 12 '.js' specifier(s) in TypeScript source:
    packages/utils/src/index.ts:1  './errors.js'
    ...
✗ 1 bare @sim/* barrel import(s):
    apps/sim/lib/embeddings/client.ts:1  '@sim/utils'

It scans only bundler-compiled source — vitest and standalone bun run scripts resolve .js → .ts themselves, so flagging their specifiers would be noise (11 such pre-existing cases are correctly ignored).

Note on the underlying gap

This is the second bug in two days that CI could not see because CI builds with webpack while developers run Turbopack. The other was the triggers↔blocks init cycle (#6342), which also produced a dev-only 500 while next build stayed green. Worth considering a next build --turbopack job, or a cheap route module-init smoke test, so dev-only resolution and initialization failures are caught before merge rather than by whoever pulls staging next.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Relevant tests are passing
• No new warnings introduced

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 7, 2026 12:14am

[cursor]

PR Summary

Low Risk
Import-path and CI-guard changes only; no auth, data, or runtime logic changes beyond fixing module resolution for dev.

Overview
Fixes local dev 500s when Turbopack loads @sim/utils: sibling re-exports in packages/utils/src/index.ts no longer use .js extensions (webpack in CI rewrote them to .ts; Turbopack does not).

apps/sim/lib/embeddings/client.ts now imports chunkArray from @sim/utils/helpers instead of the bare @sim/utils barrel, matching the documented subpath convention and avoiding pulling the whole barrel.

Adds scripts/check-import-specifiers.ts and a Import specifier hygiene audit step in test-build.yml (bun run check:import-specifiers) so unresolved first-party specifiers and bare @sim/utils barrel imports fail CI before they pass webpack-only builds.

^{Reviewed by Cursor Bugbot for commit f1c0fce. Configure here.}

[greptile-apps]

Greptile Summary

The PR removes Turbopack-incompatible .js specifiers from @sim/utils, switches the embeddings client to the documented utility subpath, and adds a CI audit for unresolved first-party imports.

• Resolves relative utility exports without explicit JavaScript extensions.
• Scans Sim, Realtime, Docs, and package TypeScript sources, including static imports, dynamic imports, re-exports, and lazy require() calls.
• Resolves workspace aliases and package export maps, and rejects bare @sim/utils barrel imports.
• Wires the audit into the repository scripts and test-build workflow.
• Regenerates tool metadata to keep generated output synchronized.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
scripts/check-import-specifiers.ts	Adds first-party specifier resolution auditing; the previously reported require-syntax and Docs coverage gaps are addressed at current HEAD.
packages/utils/src/index.ts	Removes explicit .js suffixes from utility barrel exports so Turbopack resolves the TypeScript source files.
apps/sim/lib/embeddings/client.ts	Replaces the bare utility barrel import with the documented helpers subpath.
.github/workflows/test-build.yml	Adds the import-specifier audit to CI before build and test execution.
package.json	Exposes the new audit through the check:import-specifiers script.
apps/sim/tools/generated/tool-metadata.ts	Refreshes generated tool metadata without introducing a review finding.

_{Reviews (4): Last reviewed commit: "refactor(scripts): trim the specifier au..." | Re-trigger Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 9b7921f. Configure here.}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 3f7c152. Configure here.}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f1c0fce. Configure here.}