You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:sqlite #214
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ◆ squad> ▌ │
│ Tab completes · ↑↓ history │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[CLI subprocess] node:internal/modules/esm/translators:356
[CLI subprocess] throw new ERR_UNKNOWN_BUILTIN_MODULE(url);
[CLI subprocess] ^
[CLI subprocess] Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:sqlite
[CLI subprocess] at ModuleLoader.builtinStrategy (node:internal/modules/esm/translators:356:11)
[CLI subprocess] at #translate (node:internal/modules/esm/loader:437:12)
[CLI subprocess] at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:484:27) {
[CLI subprocess] code: 'ERR_UNKNOWN_BUILTIN_MODULE'
[CLI subprocess] }
[CLI subprocess] Node.js v22.12.0
If you need more info, let me know. I installed I think what was probably 0.5.4 a couple of days ago, saw that many things changed so thought I'd uprgade. The migration is kind of half-broken for me so I thought while waiting on #199 to be ready to just init from fresh on another project idea, and that's when I got this error above.
Upgrading Node from v22.12.0 to v24.14.0 helped to get rid of that issue. However, I'm now no longer sure, based on this, I'm under the impression that the squad no longer needs to be started from copilot cli, but just from my terminal if I rune squad, that should be enough?
I'm asking because when I type in anything, even /help, the terminal kind of flickers and nothing happens. It seems to be working fine through copilot cli though. This is what it looks like running /help for example, it's as if nothing had happened:
Sorry you hit that node:sqlite import error, @tihomir-kit! Node.js built-in module resolution is tricky, and we've got that fixed now. Thanks for the detailed reproduction and environment info—that helped us track it down fast. Upgrade and you should be good! 🚀
Activity
tihomir-kit commentedon Mar 6, 2026
Upgrading Node from v22.12.0 to v24.14.0 helped to get rid of that issue. However, I'm now no longer sure, based on this, I'm under the impression that the squad no longer needs to be started from copilot cli, but just from my terminal if I rune
squad, that should be enough?I'm asking because when I type in anything, even
/help, the terminal kind of flickers and nothing happens. It seems to be working fine through copilot cli though. This is what it looks like running/helpfor example, it's as if nothing had happened:fix: resolve 4 runtime bugs (#214, #207, #206, #193)
Merge PR #234: Runtime bug fixes (4 issues)
bradygaster commentedon Mar 7, 2026
Fixed by PR #234 (merged to dev).
bradygaster commentedon Mar 7, 2026
Sorry you hit that node:sqlite import error, @tihomir-kit! Node.js built-in module resolution is tricky, and we've got that fixed now. Thanks for the detailed reproduction and environment info—that helped us track it down fast. Upgrade and you should be good! 🚀
— McManus 📝, on behalf of the Squad
test: add resolution edge cases and CLI global/status integration tests
docs: update hockney history and decision record for github#214
Merge pull request github#278 from bradygaster/squad/214-resolution-t…