Build Process for Forks

Hi folks, I forked and send a PR to allow database drivers that override timezonez handling. In my case, I use all strings on the backend with postgres, which only works with a small modification: https://github.com/better-auth/better-auth/pull/4298 To write tests and test this in prod, I need to wire up this fork, but I'm hitting a snag - simply building doesn't seam to produce the same output as the npm package? With my fork I'm hitting errors on vercel:
Error: The Edge Function "(...)" is referencing unsupported modules:
- __vc__ns__/0/index.js: node:sqlite
- __vc__ns__/1/index.js: node:sqlite
Error: The Edge Function "(...)" is referencing unsupported modules:
- __vc__ns__/0/index.js: node:sqlite
- __vc__ns__/1/index.js: node:sqlite
Is there any more documentation on the build process? I hope this gets merged and I can switch back to the official package, but for now I have to manually patch out the SQLite dialect to make it work, and I wonder what I am missing to produce the dist folder that you are using. Or is that a recent regression on canary?
GitHub
Add supportsDates option to allow string as timestampz from db by s...
Better Auth currently looks only at the database type to decide if it should handle timestams as Date or string. This PR extends this feature to allow customizing this behavior: // Force timest...
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?