Repository navigation
Conversation
nostr-social-duck still depends on @duckdb/node-api ^1.4.4 while relatr uses ^1.5.2, so both bindings were installed and the connection passed to the graph library failed typechecking. Override it to one version.
This was referenced Oct 12, 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
Relatr and
nostr-social-duckresolve different DuckDB versions. TypeScript rejects their shared connection, breaking typecheck at the graph integration point.Change
Use Bun's existing dependency override to resolve one version; update the lockfile and changeset. No graph-policy change.
Verification
bun run lintandbun run build: pass.bun test src/tests: 209 pass, 5 skip, 0 fail.manager.ts:44SDKauthUsererror remains.Checked independently on Bun 1.3.14/macOS with a temporary
SERVER_SECRET_KEYfor the benchmark. Recommended first merge; other PRs do not require this for runtime behavior.Related: #16, #17, #18, #19. All branches are independent; combined suite: 221 pass, 5 skip, 0 fail.