c4a5bf5bc0
## What? There was a dependency missing that would immediately cause issues. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-2686 |
||
|---|---|---|
| .. | ||
| app | ||
| assets | ||
| public | ||
| .gitignore | ||
| middleware.ts | ||
| next.config.js | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
SuperTokens App with Next.js app directory
This is a simple application that is protected by SuperTokens. This app uses the Next.js app directory.
How to use
Using create-next-app
- Execute
create-next-appwith npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example with-supertokens with-supertokens-app
yarn create next-app --example with-supertokens with-supertokens-app
pnpm create next-app --example with-supertokens with-supertokens-app
-
Run
yarn install -
Run
npm run devto start the application onhttp://localhost:3000.
Using create-supertokens-app
- Run the following command
npx create-supertokens-app@latest --frontend=next
- Select the option to use the app directory
Follow the instructions after create-supertokens-app has finished
Notes
- To know more about how this app works and to learn how to customise it based on your use cases refer to the SuperTokens Documentation
- We have provided development OAuth keys for the various built-in third party providers in the
/app/config/backend.tsfile. Feel free to use them for development purposes, but please create your own keys for production use.