Docs: Next.js 15 updates

docs/02-app/01-building-your-application/11-upgrading/02-version-15.mdx

@@ -35,21 +35,30 @@ bun add next@15.0.0-rc react@rc react-dom@rc eslint-config-next@15.0.0-rc
 
 [`fetch` requests](/docs/app/api-reference/functions/fetch) are no longer cached by default.
 
-To opt all `fetch` requests in a route into caching, you can use the `export const fetchCache = 'default-cache'` [segment config option](/docs/app/api-reference/file-conventions/route-segment-config).
+To opt specific `fetch` requests into caching, you can pass the `cache: 'force-cache'` option.
 
 ```js filename="app/layout.js"
-// Since this is the root layout, all fetch requests in the app will be cached.
-export const fetchCache = 'default-cache'
+export default async function RootLayout() {
+  const a = await fetch('https://...') // Not Cached
+  const b = await fetch('https://...', { cache: 'force-cache' }) // Cached
 
-export default function RootLayout() {
   // ...
 }
 ```
 
-To opt specific `fetch` requests into caching, you can pass the `cache: 'force-cache'` option.
+To opt all `fetch` requests in a layout or page into caching, you can use the `export const fetchCache = 'default-cache'` [segment config option](/docs/app/api-reference/file-conventions/route-segment-config). If individual `fetch` requests specify a `cache` option, that will be used instead.
+
+```js filename="app/layout.js"
+// Since this is the root layout, all fetch requests in the app
+// that don't set their own cache option will be cached.
+export const fetchCache = 'default-cache'
 
-```js filename="app/page.js"
-fetch('https://...', { cache: 'force-cache' })
+export default async function RootLayout() {
+  const a = await fetch('https://...') // Cached
+  const b = await fetch('https://...', { cache: 'no-store' }) // Not cached
+
+  // ...
+}
 ```
 
 ## Route Handlers
@@ -95,3 +104,37 @@ import { Inter } from '@next/font/google'
 // After
 import { Inter } from 'next/font/google'
 ```
+
+## bundlePagesRouterDependencies
+
+`experimental.bundlePagesExternals` is now stable and renamed to `bundlePagesRouterDependencies`.
+
+```js filename="next.config.js"
+/** @type {import('next').NextConfig} */
+const nextConfig = {
+  // Before
+  bundlePagesExternals: true,
+
+  // After
+  bundlePagesRouterDependencies: true,
+}
+
+module.exports = nextConfig
+```
+
+## serverExternalPackages
+
+`experimental.serverComponentsExternalPackages` is now stable and renamed to `serverExternalPackages`.
+
+```js filename="next.config.js"
+/** @type {import('next').NextConfig} */
+const nextConfig = {
+  // Before
+  serverComponentsExternalPackages: ['package-name'],
+
+  // After
+  serverExternalPackages: ['package-name'],
+}
+
+module.exports = nextConfig
+```

docs/02-app/02-api-reference/02-file-conventions/01-metadata/app-icons.mdx

@@ -169,6 +169,7 @@ export default function Icon() {
 > - By default, generated icons are [**statically optimized**](/docs/app/building-your-application/rendering/server-components#static-rendering-default) (generated at build time and cached) unless they use [dynamic functions](/docs/app/building-your-application/rendering/server-components#server-rendering-strategies#dynamic-functions) or uncached data.
 > - You can generate multiple icons in the same file using [`generateImageMetadata`](/docs/app/api-reference/functions/generate-image-metadata).
 > - You cannot generate a `favicon` icon. Use [`icon`](#icon) or a [favicon.ico](#favicon) file instead.
+> - App icons are special Route Handlers that is cached by default unless it uses a [dynamic function](/docs/app/building-your-application/caching#dynamic-functions) or [dynamic config](/docs/app/building-your-application/caching#segment-config-options) option.
 
 ### Props
 

docs/02-app/02-api-reference/02-file-conventions/01-metadata/index.mdx

@@ -9,3 +9,5 @@ This section of the docs covers **Metadata file conventions**. File-based metada
 Each file convention can be defined using a static file (e.g. `opengraph-image.jpg`), or a dynamic variant that uses code to generate the file (e.g. `opengraph-image.js`).
 
 Once a file is defined, Next.js will automatically serve the file (with hashes in production for caching) and update the relevant head elements with the correct metadata, such as the asset's URL, file type, and image size.
+
+> **Good to know**: Special Route Handlers like [`sitemap.ts`](/docs/app/api-reference/file-conventions/metadata/sitemap), [`opengraph-image.tsx`](/docs/app/api-reference/file-conventions/metadata/opengraph-image), and [`icon.tsx`](/docs/app/api-reference/file-conventions/metadata/app-icons), and other [metadata files](/docs/app/api-reference/file-conventions/metadata) are cached by default.

docs/02-app/02-api-reference/02-file-conventions/01-metadata/manifest.mdx

@@ -21,6 +21,8 @@ Add or generate a `manifest.(json|webmanifest)` file that matches the [Web Manif
 
 Add a `manifest.js` or `manifest.ts` file that returns a [`Manifest` object](#manifest-object).
 
+> Good to know: `manifest.js` is special Route Handlers that is cached by default unless it uses a [dynamic function](/docs/app/building-your-application/caching#dynamic-functions) or [dynamic config](/docs/app/building-your-application/caching#segment-config-options) option.
+
 ```ts filename="app/manifest.ts" switcher
 import type { MetadataRoute } from 'next'
 

docs/02-app/02-api-reference/02-file-conventions/01-metadata/opengraph-image.mdx

@@ -86,6 +86,7 @@ Generate a route segment's shared image by creating an `opengraph-image` or `twi
 >
 > - By default, generated images are [**statically optimized**](/docs/app/building-your-application/rendering/server-components#static-rendering-default) (generated at build time and cached) unless they use [dynamic functions](/docs/app/building-your-application/rendering/server-components#server-rendering-strategies#dynamic-functions) or uncached data.
 > - You can generate multiple Images in the same file using [`generateImageMetadata`](/docs/app/api-reference/functions/generate-image-metadata).
+> - `opengraph-image.js` and `twitter-image.js` are special Route Handlers that is cached by default unless it uses a [dynamic function](/docs/app/building-your-application/caching#dynamic-functions) or [dynamic config](/docs/app/building-your-application/caching#segment-config-options) option.
 
 The easiest way to generate an image is to use the [ImageResponse](/docs/app/api-reference/functions/image-response) API from `next/og`.
 

docs/02-app/02-api-reference/02-file-conventions/01-metadata/robots.mdx

@@ -19,6 +19,8 @@ Sitemap: https://acme.com/sitemap.xml
 
 Add a `robots.js` or `robots.ts` file that returns a [`Robots` object](#robots-object).
 
+> **Good to know**: `robots.js` is a special Route Handlers that is cached by default unless it uses a [dynamic function](/docs/app/building-your-application/caching#dynamic-functions) or [dynamic config](/docs/app/building-your-application/caching#segment-config-options) option.
+
 ```ts filename="app/robots.ts" switcher
 import type { MetadataRoute } from 'next'
 

docs/02-app/02-api-reference/02-file-conventions/01-metadata/sitemap.mdx

@@ -41,6 +41,8 @@ For smaller applications, you can create a `sitemap.xml` file and place it in th
 
 You can use the `sitemap.(js|ts)` file convention to programmatically **generate** a sitemap by exporting a default function that returns an array of URLs. If using TypeScript, a [`Sitemap`](#returns) type is available.
 
+> **Good to know**: `sitemap.js` is a special Route Handlers that is cached by default unless it uses a [dynamic function](/docs/app/building-your-application/caching#dynamic-functions) or [dynamic config](/docs/app/building-your-application/caching#segment-config-options) option.
+
 ```ts filename="app/sitemap.ts" switcher
 import type { MetadataRoute } from 'next'