Add support for importing translation files directly

[k0d13]

Replace the compile step with support for importing the translation files directly
Closes #18

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
saykit	Skipped		Apr 26, 2026 3:06am

[changeset-bot]

🦋 Changeset detected

Latest commit: 228d887

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
unplugin-saykit	Patch
babel-plugin-saykit	Patch
@saykit/format-po	Patch
@saykit/config	Patch
@saykit/transform-js	Patch
@saykit/transform-jsx	Patch

Not sure what this means? Click here to learn what changesets are.

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

[greptile-apps]

Greptile Summary

This PR replaces the two-step extract → compile workflow with a single extract step, enabling direct import of .po translation files at build time via Babel and unplugin transform hooks. The compile/build workers and the fallbackLocales config field are removed, .d.ts type declarations are generated alongside each locale file, and the hash function is made URL-safe.

Confidence Score: 5/5

Safe to merge; only a single P2 finding about error reporting in watch mode that doesn't affect the happy path.

All findings are P2 or lower. The core inline-import feature (babel + unplugin load hooks, .d.ts generation, hash URL-safety) is implemented correctly. The watch-mode error suppression is a UX gap but doesn't affect normal extraction or the new direct-import feature.

packages/config/src/commands/extract.ts — watch + allSettled interaction

Prompt To Fix All With AI

This is a comment left during a code review.
Path: packages/config/src/commands/extract.ts
Line: 23-29

Comment:
**Error reporting unreachable in watch mode**

When `--watch` is active, each bucket's task `await`s `worker.watch()`, which is an infinite loop and never resolves. `Promise.allSettled(tasks)` therefore never settles, so the `AggregateError` block is never reached. If one bucket fails during `scan()` / `write()` while another is watching, the failure is logged but never surfaced as a thrown error — the CLI appears to be running correctly while silently ignoring one bucket's failure.

A common pattern is to run the scan/write phase with `Promise.all` first (letting it throw immediately on failure), then start watch loops independently:
```ts
await Promise.all(
  workers.map(async (w) => { await w.scan(); await w.write(); }),
);
if (options.watch) await Promise.all(workers.map((w) => w.watch()));
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (4): Last reviewed commit: "Remove fallback references from docs" | Re-trigger Greptile}