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
I am trying to get a standalone build working with @payloadcms/db-sqlite. However, neither running the build natively nor using a container with the provided Dockerfile template works for me. For example, when I attempt to access the initial /admin/create-first-user route after starting the native build, I encounter the following error:
I have also tried including @libsql/client and libsql as project dependencies, as previously mentioned in #7527, it did not resolve the issue for me. Upon inspecting the node_modules directory in the resulting build, I noticed that the prebuilt binary package for @libsql is missing. This leads me to suspect that the issue might be related to the standalone bundling process in Next.js.
Describe the Bug
Hi,
I am trying to get a standalone build working with
@payloadcms/db-sqlite
. However, neither running the build natively nor using a container with the provided Dockerfile template works for me. For example, when I attempt to access the initial/admin/create-first-user
route after starting the native build, I encounter the following error:I have also tried including
@libsql/client
andlibsql
as project dependencies, as previously mentioned in #7527, it did not resolve the issue for me. Upon inspecting thenode_modules
directory in the resulting build, I noticed that the prebuilt binary package for@libsql
is missing. This leads me to suspect that the issue might be related to the standalone bundling process in Next.js.@DanRibbens
Link to the code that reproduces this issue
https://github.com/janeumnn/payload-reproduction-bug
Reproduction Steps
cd payload-reproduction-bug && pnpm install
.pnpm build
.cp -r .next/static .next/standalone/.next/
.node server.js
.Which area(s) are affected? (Select all that apply)
db-sqlite
Environment Info
The text was updated successfully, but these errors were encountered: