From f4f87e4fc0656eda36bc30c294c5855e6f113ea6 Mon Sep 17 00:00:00 2001 From: Akshay Raj A Date: Tue, 14 Oct 2025 15:20:09 +0530 Subject: [PATCH] docs: add support for yarn, pnpm, and bun in setup environment section --- docs/pages/getting-started/installation.mdx | 35 ++++++++++++++++++++- 1 file changed, 34 insertions(+), 1 deletion(-) diff --git a/docs/pages/getting-started/installation.mdx b/docs/pages/getting-started/installation.mdx index e0b5741ff3..5f65b3e046 100644 --- a/docs/pages/getting-started/installation.mdx +++ b/docs/pages/getting-started/installation.mdx @@ -46,8 +46,41 @@ Start by installing the appropriate package for your framework. The only environment variable that is mandatory is the `AUTH_SECRET`. This is a random value used by the library to encrypt tokens and email verification hashes. (See [Deployment](/getting-started/deployment) to learn more). You can generate one via the official [Auth.js CLI](https://cli.authjs.dev) running: + + + + ```bash npm2yarn + npx auth secret + ``` + + + + + ```bash npm2yarn + npx auth secret + ``` + + + + + ```bash npm2yarn + npx auth secret + ``` + + + + + ```bash npm2yarn + npx auth secret + ``` + + + + +Alternatively, you can use bun: + ```bash -npx auth secret +bunx auth secret ``` This will also add it to your `.env` file, respecting the framework conventions (eg.: Next.js' `.env.local`).