new·Earn with mozg — 20% of every monthSend somebody here and take a fifth of every plan payment they make, for as long as they keep paying — not a bounty on the first invoice. Your handle is the link, the window is thirty days, and the commission lands on your balance the second they pay. Free to join: if you have signed in, you already have the link. mozg.sh/earnall news →
mozg.beta
Sign in

Better Auth · Reference · all subjects

cli & setup

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

pnpm is the required package manager for Better Auth

pnpm must be installed to manage dependencies in Better Auth development. It is used for installing packages with 'pnpm install' and running commands.

Node.JS LTS required for Better Auth development

Node.JS must be installed to develop Better Auth, preferably on an LTS (Long Term Support) version.

Development setup steps for Better Auth

To set up Better Auth development: 1) Fork the repository at https://github.com/better-auth/better-auth, 2) Clone the fork with 'git clone https://github.com/YOUR-USERNAME/better-auth.git' and cd into it, 3) Install dependencies with 'pnpm install', 4) Copy the example env file with 'cp -n ./docs/.env.example ./docs/.env'.

Development branch workflow

To start development: add the upstream remote with 'git remote add upstream https://github.com/better-auth/better-auth.git', ensure you are on main with 'git checkout main', pull latest changes with 'git pull upstream main', then create and switch to a new branch with 'git checkout -b feature/your-feature-name'.

Running development servers

Run the main development server with 'pnpm dev'. To start only the docs server, run 'pnpm -F docs dev'.

Give your agent this brain