files updated using the pnpm run prettier-fix command

Author: P41T0

crates/next-error-code-swc-plugin/README.md

@@ -18,7 +18,6 @@ This plugin transforms Next.js source code by:
 ## Build Process Details
 
 - **Two-Pass Build:**
-
   1. **First Pass:**
      - Extracts new errors and temporarily stores them in `packages/next/.errors/*.json`.
      - In CI, a build with new errors will fail.
@@ -31,7 +30,6 @@ This plugin transforms Next.js source code by:
 ## Modifying the Plugin
 
 - **WASM Rebuild Required:**
-
   - After modifying the plugin, rebuild the WASM file via `pnpm build-error-code-plugin` and commit it to the repository.
   - **Reason:** Pre-built artifacts simplify the build process (`pnpm build` runs without requiring `cargo`).
 

docs/01-app/02-guides/progressive-web-apps.mdx

@@ -331,7 +331,8 @@ function InstallPrompt() {
           <span role="img" aria-label="plus icon">
             {' '}
             ➕{' '}
-          </span>.
+          </span>
+          .
         </p>
       )}
     </div>

docs/01-app/03-api-reference/02-components/image.mdx

@@ -878,7 +878,6 @@ This `next/image` component uses browser native [lazy loading](https://caniuse.c
   - Use CSS `@supports (font: -apple-system-body) and (-webkit-appearance: none) { img[loading="lazy"] { clip-path: inset(0.6px) } }`
   - Use [`priority`](#priority) if the image is above the fold
 - [Firefox 67+](https://bugzilla.mozilla.org/show_bug.cgi?id=1556156) displays a white background while loading. Possible solutions:
-
   - Enable [AVIF `formats`](#formats)
   - Use [`placeholder`](#placeholder)
 

docs/01-app/03-api-reference/03-file-conventions/route-segment-config.mdx

@@ -52,7 +52,6 @@ export const dynamic = 'auto'
 
 - **`'auto'`** (default): The default option to cache as much as possible without preventing any components from opting into dynamic behavior.
 - **`'force-dynamic'`**: Force [dynamic rendering](/docs/app/getting-started/partial-prerendering#dynamic-rendering), which will result in routes being rendered for each user at request time. This option is equivalent to:
-
   - Setting the option of every `fetch()` request in a layout or page to `{ cache: 'no-store', next: { revalidate: 0 } }`.
   - Setting the segment config to `export const fetchCache = 'force-no-store'`
 

docs/01-app/03-api-reference/04-functions/generate-metadata.mdx

@@ -113,7 +113,6 @@ export default function Page({ params, searchParams }) {}
 `generateMetadata` function accepts the following parameters:
 
 - `props` - An object containing the parameters of the current route:
-
   - `params` - An object containing the [dynamic route parameters](/docs/app/api-reference/file-conventions/dynamic-routes) object from the root segment down to the segment `generateMetadata` is called from. Examples:
 
     | Route                           | URL         | `params`                  |
@@ -230,11 +229,9 @@ export const metadata = {
 > **Good to know**:
 >
 > - `title.template` applies to **child** route segments and **not** the segment it's defined in. This means:
->
 >   - `title.default` is **required** when you add a `title.template`.
 >   - `title.template` defined in `layout.js` will not apply to a `title` defined in a `page.js` of the same route segment.
 >   - `title.template` defined in `page.js` has no effect because a page is always the terminating segment (it doesn't have any children route segments).
->
 > - `title.template` has **no effect** if a route has not defined a `title` or `title.default`.
 
 ##### `absolute`
@@ -284,11 +281,9 @@ export const metadata = {
 > **Good to know**:
 >
 > - `layout.js`
->
 >   - `title` (string) and `title.default` define the default title for child segments (that do not define their own `title`). It will augment `title.template` from the closest parent segment if it exists.
 >   - `title.absolute` defines the default title for child segments. It ignores `title.template` from parent segments.
 >   - `title.template` defines a new title template for child segments.
->
 > - `page.js`
 >   - If a page does not define its own title the closest parents resolved title will be used.
 >   - `title` (string) defines the routes title. It will augment `title.template` from the closest parent segment if it exists.

errors/css-global.mdx

@@ -21,8 +21,9 @@ Consider the stylesheet named [`styles.css`](/docs/app/getting-started/css)
 
 ```css filename="styles.css"
 body {
-  font-family: 'SF Pro Text', 'SF Pro Icons', 'Helvetica Neue', 'Helvetica',
-    'Arial', sans-serif;
+  font-family:
+    'SF Pro Text', 'SF Pro Icons', 'Helvetica Neue', 'Helvetica', 'Arial',
+    sans-serif;
   padding: 20px 20px 60px;
   max-width: 680px;
   margin: 0 auto;

errors/no-styled-jsx-in-document.mdx

@@ -16,8 +16,9 @@ For example, consider the following stylesheet named `styles.css`:
 
 ```css filename="styles.css"
 body {
-  font-family: 'SF Pro Text', 'SF Pro Icons', 'Helvetica Neue', 'Helvetica',
-    'Arial', sans-serif;
+  font-family:
+    'SF Pro Text', 'SF Pro Icons', 'Helvetica Neue', 'Helvetica', 'Arial',
+    sans-serif;
   padding: 20px 20px 60px;
   max-width: 680px;
   margin: 0 auto;

examples/auth0/components/layout.tsx

@@ -30,8 +30,9 @@ const Layout = ({ user, loading = false, children }: LayoutProps) => {
         body {
           margin: 0;
           color: #333;
-          font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto,
-            Oxygen, Ubuntu, Cantarell, "Open Sans", "Helvetica Neue", sans-serif;
+          font-family:
+            -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen,
+            Ubuntu, Cantarell, "Open Sans", "Helvetica Neue", sans-serif;
         }
       `}</style>
     </>

examples/cms-sitecore-xmcloud/src/lib/extract-path/index.ts

@@ -19,7 +19,7 @@ export class PathExtractor {
     }
     let path = Array.isArray(params.path)
       ? params.path.join("/")
-      : params.path ?? "/";
+      : (params.path ?? "/");
 
     // Ensure leading '/'
     if (!path.startsWith("/")) {

examples/cms-wordpress/README.md

@@ -89,7 +89,6 @@ Deploy it to the cloud with [Vercel](https://vercel.com/new?utm_source=github&ut
    - WPGraphQL for ACF (optional)
 6. Do first-time install of Redirection. Recommended to enable monitor of changes
 7. Configure Yoast SEO with:
-
    - Disable XML Sitemaps under Yoast SEO -> Settings
    - If you did not change the `Site Address (URL)` before installing Yoast, it will ask you to run optimize SEO data after changing permalinks, do so
    - Generate a robots.txt file under Yoast SEO -> Tools -> File Editor