Cannot use libsql in production
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- deno, typescript
- Domain
- build-system
Research direction
The failure occurs in the built _fresh/server/server-entry.mjs when it cannot resolve @libsql/darwin-arm64; the report also links a reproduction repository. Read the build and server startup paths that bundle npm dependencies, then reproduce with deno task build and deno task start. Done means the reproduced libsql client starts successfully after a production build.
Written by the indexing model from the issue text.
Description
I started a small project to experiment with fresh and certain packages I tend to use.
This also includes drizzle and using libsql as a database driver.
When using the vite dev-server (deno task dev) everything is fine. After running deno task build and starting the project (deno task start), I received this error:
Task start deno serve -A _fresh/server.js
error: Uncaught (in promise) Error: Cannot find module '@libsql/darwin-arm64'
Require stack:
- <path>/fresh-libsql/_fresh/server/server-entry.mjs
at Module._resolveFilename (node:module:633:15)
at Module._load (node:module:496:27)
at Module.require (node:module:694:19)
at require (node:module:828:16)
at requireNative (file:///<path>/fresh-libsql/_fresh/server/server-entry.mjs:6359:10)
at file:///<path>/fresh-libsql/_fresh/server/server-entry.mjs:6361:442
I created a repository to replicate & isolate the issue: https://github.com/DontMash/fresh-libsql
fresh: v2.1.4
deno: v2.5.4
Steps to reproduce:
-
Setup a new fresh project
deno run -Ar jsr:@fresh/init -
Add @libsql/client package
deno add npm:@libsql/client -
Use the package to create a client
... const turso = createClient({ url: "file:local.db", }); ... -
Build the project
deno task build -
Try running the project (will fail)
deno task start
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 757
- Avg merge
- 3m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from freshframework/fresh
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
freshframework/fresh#3920 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
freshframework/fresh#3833 ·
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
freshframework/fresh#3803 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
freshframework/fresh#3918 · 1 comment · 4 reactions ·
-
Tab title doesn't update to <Head> <title> when navigating to a page with another <title>Possibly taken @1AbdullahButt claimed this 7 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 57/100
freshframework/fresh#3916 ·
All issues in freshframework/fresh
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tintinweb/pi-subagents#459 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
danielmiessler/LifeOS#2830 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day