Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot find compiled sqlite-vec (breaking change betseen 0.1.2-alpha.9 and 0.1.2-alpha.10) #107

Open
tobowers opened this issue Sep 16, 2024 · 3 comments

Comments

@tobowers
Copy link

minimal failing code: https://github.com/tobowers/minimal-failing-sql-vec-nextjs (ignore the nextjs name there, that's my previous example).

When running 0.1.2-alpha.9 the code works great, but when upping to 0.1.2-alpha.10 (or later) the code fails with the below:

tests/works.spec.ts:
43 | "..",
44 | packageName,
45 | ${ENTRYPOINT_BASE_NAME}.${extensionSuffix(platform)}
46 | );
47 | if (!statSync(loadablePath, { throwIfNoEntry: false })) {
48 | throw new Error(extensionNotFoundErrorMessage(packageName));
^
error: Loadble extension for sqlite-vec not found. Was the sqlite-vec-darwin-arm64 package installed?
at getLoadablePath (/Users/tobowers/code/minimal-vec-failure/node_modules/sqlite-vec/index.mjs:48:11)
at load (/Users/tobowers/code/minimal-vec-failure/node_modules/sqlite-vec/index.mjs:55:20)
at getDatabase (/Users/tobowers/code/minimal-vec-failure/index.ts:11:13)
at /Users/tobowers/code/minimal-vec-failure/tests/works.spec.ts:6:16
✗ sqlite-vec > should work [1.23ms]

Environment:
MacOs
Bun version: 1.1.28

Seems related to #45 as well.

@asg017
Copy link
Owner

asg017 commented Sep 16, 2024

Can confirm this is a bug, looking into a fix now, thanks for reporting!

@asg017
Copy link
Owner

asg017 commented Sep 16, 2024

@tobowers can you try with [email protected] and let me know if it works? I tried it manually on my side and it seems to have fixed it.

Problem was introduced with some changes I made to the packaging workflow, which incorrectly combined different platform packages (windows library was included in the macos npm package, etc.). Though the latest release should have fixed it.

Will release a stable [email protected] once I confirm it all works, apologies again for bug. And thanks a ton for reporting so quickly!

@tobowers
Copy link
Author

fixed it for me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants