3 commits

Author	SHA1	Message	Date
Dev Agrawal	9e978cf64f	with-clerk example updated to app router (#49717) ... <!-- 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 or adding/fixing 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? Updates the `with-clerk` example to use the app router and latest version of `@clerk/nextjs` ### Why? ### How? Closes NEXT- Fixes # --> Updates the `with-clerk` example to use the app router and latest version of `@clerk/nextjs`	2023-05-15 22:25:43 +00:00
Colin Sidoti	713a5aa701	Use new @clerk/nextjs package in with-clerk example, update Next.js authentication docs (#28906) ... * Update headings to clarify that we're describing. Add heading for Authentication API Routes * Start adding API route examples * Start adding API route examples * Start adding API route examples * Start adding API route examples * auth: Replace clerk packages with @clerk/nextjs * Add API authentication example to with-clerk * Fix footer links * Proofread, ensure consistency * Update example's props to use new version * Update example links * Add rel tag to _blank link * Obscure the authentication provider in the example * Replace example * Reset authentication docs, list Clerk as vendor * Re-fix typo * Change sample to example * Add the example * Update examples/with-clerk/package.json Co-authored-by: Lee Robinson <me@leerob.io> Co-authored-by: Peter Perlepes <p.perlepes@gmail.com> Co-authored-by: Lee Robinson <me@leerob.io>	2021-09-17 10:54:34 -05:00
Sokratis Vidros	dfe1b05ff5	Add Clerk.dev example (#24311) ... ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. ## Documentation / Examples - [x] Make sure the linting passes	2021-04-21 18:59:45 +00:00