docs: update fumadocs dependencies (#11594)

This PR upgrade Fuma docs and alings some code snippets since shiki
3.22.0 does no longer include defaults for `curl`.
This commit is contained in:
Florian Forster
2026-02-17 21:41:48 +01:00
committed by GitHub
parent 93a4ed8857
commit d17e954f26
7 changed files with 323 additions and 132 deletions
+1 -1
View File
@@ -149,7 +149,7 @@ Now go to Token settings and check the checkbox for **User Info inside ID Token*
Create a file `.env` in the root of the project and add the following keys to it.
You can find your Issuer Url on the application detail page in console.
```env reference
```bash reference
https://github.com/zitadel/zitadel-nextjs/blob/main/.env.example
```
@@ -58,7 +58,7 @@ Depending on your authentication method you'll need additional headers and param
Send your `client_id` and `client_secret` as Basic Auth Header. Note that OAuth2 requires client_id and client_secret to be form url encoded.
So check [Client Secret Basic Auth Method](/apis/openidoauth/authn-methods#client-secret-basic) on how to build it correctly.
```curl
```bash
curl --request POST \
--url ${CUSTOM_DOMAIN}/oauth/v2/token \
--header 'Authorization: Basic ${basic}' \
@@ -60,7 +60,7 @@ Depending on your authentication method you'll need additional headers and param
Send a JWT in the `client_assertion` and set the `client_assertion_type` to `urn:ietf:params:oauth:client-assertion-type:jwt-bearer`
for us to validate the signature against the registered public key:
```curl
```bash
curl --request POST \
--url ${CUSTOM_DOMAIN}/oauth/v2/token \
--header 'Content-Type: application/x-www-form-urlencoded' \
@@ -67,7 +67,7 @@ Depending on your authentication method you'll need additional headers and param
Send your `client_id` and the previously generated string as `code_verifier` for us to recompute the `code_challenge` of the authorization request:
```curl
```bash
curl --request POST \
--url ${CUSTOM_DOMAIN}/oauth/v2/token \
--header 'Content-Type: application/x-www-form-urlencoded' \
@@ -51,7 +51,7 @@ Depending on your authentication method you'll need additional headers and param
Send your `client_id` and the previously generated string as `code_verifier` for us to recompute the `code_challenge` of the authorization request:
```curl
```bash
curl --request POST \
--url ${CUSTOM_DOMAIN}/oauth/v2/token \
--header 'Content-Type: application/x-www-form-urlencoded' \