tursodatabase / tursodatabase/libsql-client-ts
An error occurs when I try to run my NestJS project using Turso and i try change node version wit 20, 21 and 22. When i uninstall the dependency. The project works.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 576
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
node:internal/modules/cjs/loader:1921
return process.dlopen(module, path.toNamespacedPath(filename));
^
Error: The specified module could not be found.
\?\C:\Users\project\node_modules@libsql\win32-x64-msvc\index.node
at Object..node (node:internal/modules/cjs/loader:1921:18)
at Module.load (node:internal/modules/cjs/loader:1465:32)
at Function._load (node:internal/modules/cjs/loader:1282:12)
at TracingChannel.traceSync (node:diagnostics_channel:322:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
at Module.require (node:internal/modules/cjs/loader:1487:12)
at require (node:internal/modules/helpers:135:16)
at requireNative (C:\Users\project\node_modules\libsql\index.js:22:10)
at Object. (C:\Users\project\node_modules\libsql\index.js:45:5)
at Module._compile (node:internal/modules/cjs/loader:1730:14) {
code: 'ERR_DLOPEN_FAILED'
}
Node.js v22.17.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows failure with Node.js 20, 21, and 22, then inspect the native loading path in node_modules/libsql/index.js and the @libsql/win32-x64-msvc/index.node package. Compare behavior with the dependency removed; done means the NestJS project starts without ERR_DLOPEN_FAILED while the libSQL dependency remains installed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, sqlite, typescript
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100