From dc0f31336894fa91e39dd5402c5443c6b6b0bb6a Mon Sep 17 00:00:00 2001 From: Oakwhisper <46499091+Oakwhisper@users.noreply.github.com> Date: Fri, 10 Jan 2025 14:09:37 -0500 Subject: [PATCH 1/2] Changed npm execution command to fix pnpm translation. Fixes #12331 --- docs/pages/getting-started/deployment.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/getting-started/deployment.mdx b/docs/pages/getting-started/deployment.mdx index bcfe4f3031..d1aae68b65 100644 --- a/docs/pages/getting-started/deployment.mdx +++ b/docs/pages/getting-started/deployment.mdx @@ -14,7 +14,7 @@ import { Accordion, Accordions } from "@/components/Accordion" Auth.js libraries require you to set an `AUTH_SECRET` environment variable. This is used to encrypt cookies and tokens. It should be a cryptographically secure random string of at least 32 characters: ```bash npm2yarn -npm exec auth secret +npx auth secret ``` If you are using an [OAuth Provider](/concepts/oauth), your provider will provide you with a **Client ID** and **Client Secret** that you will need to set as environment variables as well (in the case of an OIDC provider, like Auth0, a third `issuer` value might be also required, refer to the provider's specific documentation). From 6c7f2b7f390368bb91b2d8f5befa8f627df3be3c Mon Sep 17 00:00:00 2001 From: Oakwhisper <46499091+Oakwhisper@users.noreply.github.com> Date: Thu, 16 Jan 2025 19:27:11 -0500 Subject: [PATCH 2/2] Update environment-variables.mdx Changed additional instance of npm exec --- docs/pages/guides/environment-variables.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/guides/environment-variables.mdx b/docs/pages/guides/environment-variables.mdx index d30d0604bb..e3b7b74577 100644 --- a/docs/pages/guides/environment-variables.mdx +++ b/docs/pages/guides/environment-variables.mdx @@ -39,7 +39,7 @@ AUTH_SECRET="This is an example" `AUTH_SECRET` is a random token used by the library to encrypt tokens and email verification hashes, and it's mandatory to keep things secure (See [Deployment](/getting-started/deployment) to learn more). You can use the CLI to generate an auth secret: ```bash npm2yarn -npm exec auth secret +npx auth secret ``` ## Environment Variable Inference