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
npm install @libsql/client installs @libsql/client-wasm, which has no ./http or ./web export #2185
npm install @libsql/client in a WebContainer installs @libsql/client-wasm@0.17.2 into node_modules/@libsql/client. That package only exports ".", so import("@libsql/client/http") and import("@libsql/client/web") fail with ERR_PACKAGE_PATH_NOT_EXPORTED.
Both subpaths are plain JavaScript over fetch and need no native binding, so they should work as they are. Apps that talk to a remote libSQL or Turso database import @libsql/client/http or /web on purpose, and they break only inside a WebContainer.
Some ideas, up to you: keep the real @libsql/client and swap only its native dependency, or install the wasm package with the http and web subpaths still mapped to the real ones.
Activity
github-actions commentedon Nov 17, 2026
We noticed that you did not provide a StackBlitz or Bolt reproduction link. Please update the issue and add a link to a public project.