agent-orchestrator/packages
i-trytoohard eec8ffe2ad fix(web): externalize ao-core and better-sqlite3 from Next.js bundle
Fixes #1930.

Next.js bundles @aoagents/ao-core (via transpilePackages) and bakes
import.meta.url as the build machine's absolute path into the output.
At runtime on any other machine (especially Windows), createRequire()
receives a non-existent file:// URL and fails.

Adding @aoagents/ao-core and better-sqlite3 to serverExternalPackages
tells Next.js to not bundle these — they're resolved at runtime from
node_modules, so import.meta.url resolves to the actual install path.

This fixes:
- events-db.ts: createRequire(import.meta.url)("better-sqlite3")
- update-cache.ts: createRequire(fileURLToPath(import.meta.url))
- The Windows ERR_INVALID_ARG_VALUE error in the user report
2026-05-19 22:47:03 +00:00
..
ao fix(cli): rebuild better-sqlite3 on install + quieter ABI-mismatch warning (closes #1822) (#1824) 2026-05-18 04:02:26 +05:30
cli feat(notifier): make notifier system robust with manual harness and desktop setup (#1736) 2026-05-19 14:48:40 +05:30
core refactor(agent-claude-code): split activity detection; remove dead JSONL cases; detect blocked from api_error (#1927) 2026-05-19 18:00:54 +05:30
integration-tests feat(notifier): make notifier system robust with manual harness and desktop setup (#1736) 2026-05-19 14:48:40 +05:30
notifier-macos feat(notifier): make notifier system robust with manual harness and desktop setup (#1736) 2026-05-19 14:48:40 +05:30
plugins fix(agent-claude-code): harden activity detection against 5 real-world edge cases (#1932) 2026-05-19 22:55:05 +05:30
web fix(web): externalize ao-core and better-sqlite3 from Next.js bundle 2026-05-19 22:47:03 +00:00