From 6e1ce2fd3d7f2f92bf136f4641bd36577bf6d56b Mon Sep 17 00:00:00 2001 From: Cory Deppen Date: Sat, 14 Dec 2024 12:30:23 -0500 Subject: [PATCH] docs: fix tanstack-start tab (#888) --- CONTRIBUTING.md | 18 +++++++++--------- docs/content/docs/installation.mdx | 2 +- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 721b7bf156..e3cc1ac551 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -8,7 +8,6 @@ Thanks for taking the time to improve Better Auth! This is a small document to g Probably the best way to get going is to see if there is open issues acknowledged by the team. Feel free to open an issue if you found a bug or a missing feature you'd like to work on, and there aren't any issues mentioning it. - **Framework Integrations** We aim to support as many frameworks as possible in the JavaScript ecosystem. If you'd like to integrate one we don't already cover, start by adding documentation. Since the core is designed to be flexible, a simple doc should work for most frameworks. If we believe the integration should go further to reduce friction, we might ask you to contribute or handle it ourselves. @@ -19,7 +18,7 @@ Right now, everything you need—framework integrations, plugins, and all the ne **Plugins** -If you plan to contribute a new core plugin open an issue first. If we see fit with the plans we have in mind we'll give you a green light. If not you can still publish your plugins yourself. +If you plan to contribute a new core plugin open an issue first. If we see fit with the plans we have in mind we'll give you a green light. If not you can still publish your plugins yourself. Make sure to read the plugin documentation before you start developing one. @@ -35,19 +34,20 @@ If you see any security issue we prefer you to disclose it via an email (securit - Rather than extensive configurations, focus instead on providing opinionated, best-practice defaults. - Try to make a consistent and predictable API across all supported frameworks -- Everything should be type-safe and embrace typescript magic when necessary. +- Everything should be type-safe and embrace typescript magic when necessary. ## Development 1. Fork the repo 2. clone your fork. 3. install node.js (preferable latest LTS). -4. run `pnpm i` in your terminal to install dependencies. -5. create a branch. -6. build the project using `pnpm build` -7. run `pnpm -F docs` dev (to run the docs section) -8. create a draft pull request. link the relevant issue by referring to it in the PR's description. Eg.closes #123 will link the PR to issue/pull request #123. -9. implement your changes. +4. run `cp -n ./docs/.env.example ./docs/.env` to create a `.env` file (if it doesn't exist) +5. run `pnpm i` in your terminal to install dependencies. +6. create a branch. +7. build the project using `pnpm build` +8. run `pnpm -F docs dev` (to run the docs section) +9. create a draft pull request. link the relevant issue by referring to it in the PR's description. Eg.closes #123 will link the PR to issue/pull request #123. +10. implement your changes. ## Testing diff --git a/docs/content/docs/installation.mdx b/docs/content/docs/installation.mdx index 32c4bcf70c..5f94a07e54 100644 --- a/docs/content/docs/installation.mdx +++ b/docs/content/docs/installation.mdx @@ -232,7 +232,7 @@ Create a new file or route in your framework's designated catch-all route handle Better Auth supports any backend framework with standard Request and Response objects and offers helper functions for popular frameworks. - + ```ts title="/app/api/auth/[...all]/route.ts" import { auth } from "@/lib/auth"; // path to your auth file