github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-10-18 11:32:15 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #8456] feat: use native node:crypto scrypt for Cloudflare Workers support #11096

New Issue
Closed
opened 2026-04-13 07:28:37 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 07:28:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @bauchdj on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/8456

Problem

The password hashing module currently always uses @noble/hashes/scrypt (pure JS). Cloudflare Workers now support node:crypto.scrypt, so environments like CF Workers could benefit from the faster native implementation.

Proposed Solution

  • Detect native node:crypto.scrypt at import time via dynamic import with try/catch
  • Prefer native scrypt when available (Node.js, CF Workers), fall back to @noble/hashes/scrypt
  • No change to hash format — fully backwards compatible with existing stored hashes
  • Add cross-compatibility tests to verify native and noble produce identical output
Originally created by @bauchdj on GitHub (Mar 6, 2026). Original GitHub issue: https://github.com/better-auth/better-auth/issues/8456 ## Problem The password hashing module currently always uses `@noble/hashes/scrypt` (pure JS). Cloudflare Workers now support `node:crypto.scrypt`, so environments like CF Workers could benefit from the faster native implementation. ## Proposed Solution - Detect native `node:crypto.scrypt` at import time via dynamic import with try/catch - Prefer native scrypt when available (Node.js, CF Workers), fall back to `@noble/hashes/scrypt` - No change to hash format — fully backwards compatible with existing stored hashes - Add cross-compatibility tests to verify native and noble produce identical output
GiteaMirror added the enhancementlocked labels 2026-04-13 07:28:37 -05:00
GiteaMirror commented 2026-04-13 07:28:38 -05:00
Author
Owner
Copy Link
Copy Source

@bytaesu commented on GitHub (Mar 6, 2026):

We're careful with changes that introduce runtime dependencies 🤔

<!-- gh-comment-id:4013989296 --> @bytaesu commented on GitHub (Mar 6, 2026): We're careful with changes that introduce runtime dependencies 🤔
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No labels enhancement locked
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#11096