tursodatabase / libsql

libSQL is a fork of SQLite that is both Open Source, and Open Contributions.
https://turso.tech/libsql
MIT License
11.97k stars 303 forks source link

Error: The specified module could not be found. `\node_modules\@libsql\win32-x64-msvc\index.node` #1797

Open vvhybe opened 1 month ago

vvhybe commented 1 month ago

I got this error only on the Windows machine I've tried it on Linux (Ubuntu) in the WSL It works fine, except for Windows, I think because it's missing the compiled binaries from @libsql\win32-x64-msvc I tried installing it manually and adding it into production dependencies using both npm and pnpm but no chance *(i rolled out on all the boring processes deleting pkg manager cache, etc...)

My Machine

My stack:

{
  "dependencies": {
      "@libsql/client": "^0.14.0",
      "@libsql/win32-x64-msvc": "^0.4.6",
      "drizzle-orm": "^0.35.3",
  }
}

Screenshot might help:

image

Honestly, I have doubts that this error is coming from the drizzle orm itself, so i drop the same issue in the drizzle GitHub repo https://github.com/drizzle-team/drizzle-orm/issues/3205

Johnkat-Mj commented 3 weeks ago

I am also facing this error,

Hey @vvhybe have you found a solution? It seems to be a problem related to libsql on win11 On win10 it works well

vvhybe commented 3 weeks ago

I am also facing this error,

Hey @vvhybe have you found a solution? It seems to be a problem related to libsql on win11 On win10 it works well

@Johnkat-Mj, you have confirmed my doubts about the problem that occurs only on WIN 11 using the libsql pkg. because I have tried to resolve that error as you saw on the Issue I thought at first it drizzle that's caused the stack of errors and not compatible with libsql on Windows, I have tried installing the Windows compiled binaries for libsql but no chance and I couldn't find any solution, so I decided to switch all my development into Linux (Ubuntu), after I tested it on WSL and it works fine

Now you said it works fine on Win 10 I think it may have to do with something related to Win 11 or Powershell execution policy.!

If you dropped on any possible way to resolve this error inform me.