docs: update nextjs documentation

Author: xiaoyu2er

apps/docs/content/en/docs/01-app/02-guides/memory-usage.mdx

@@ -136,3 +136,36 @@ You can disable source map generation by adding `productionBrowserSourceMaps: fa
 ## Edge memory issues
 
 Next.js `v14.1.3` fixed a memory issue when using the Edge runtime. Please update to this version (or later) to see if it addresses your issue.
+
+## Preloading Entries
+
+When the Next.js server starts, it preloads each page's JavaScript modules into memory, rather than at request time.
+
+This optimization allows for faster response times, in exchange for a larger initial memory footprint.
+
+To disable this optimization, set the `experimental.preloadEntriesOnStart` flag to `false`.
+
+```ts filename="next.config.ts" switcher
+import type { NextConfig } from 'next'
+
+const config: NextConfig = {
+  experimental: {
+    preloadEntriesOnStart: false,
+  },
+}
+
+export default config
+```
+
+```js filename="next.config.mjs" switcher
+/** @type {import('next').NextConfig} */
+const config = {
+  experimental: {
+    preloadEntriesOnStart: false,
+  },
+}
+
+export default config
+```
+
+Next.js doesn't unload these JavaScript modules, meaning that even with this optimization disabled, the memory footprint of your Next.js server will eventually be the same if all pages are eventually requested.

apps/docs/content/en/docs/01-app/05-api-reference/04-functions/generate-metadata.mdx

@@ -102,7 +102,7 @@ export default function Page({ params, searchParams }) {}
 > - The `metadata` object and `generateMetadata` function exports are **only supported in Server Components**.
 > - You cannot export both the `metadata` object and `generateMetadata` function from the same route segment.
 > - `fetch` requests inside `generateMetadata` are automatically [memoized](/docs/app/deep-dive/caching#request-memoization) for the same data across `generateMetadata`, `generateStaticParams`, Layouts, Pages, and Server Components.
-> - React [`cache` can be used](/docs/app/deep-dive/caching#react-cache-function) if `fetch` is unavailable. -[ File-based metadat](/docs/app/api-reference/file-conventions/metadata) has the higher priority and will override the `metadata` object and `generateMetadata` function.
+> - React [`cache` can be used](/docs/app/deep-dive/caching#react-cache-function) if `fetch` is unavailable. -[ File-based metadata](/docs/app/api-reference/file-conventions/metadata) has the higher priority and will override the `metadata` object and `generateMetadata` function.
 
 ## Reference
 

apps/docs/content/en/docs/01-app/05-api-reference/05-config/01-next-config-js/turbopack.mdx

@@ -49,7 +49,7 @@ The following options are available for the `turbo` configuration:
 
 ### Supported loaders
 
-The following loaders have been tested to work with Turbopack's webpack loader implementation:
+The following loaders have been tested to work with Turbopack's webpack loader implementation, but many other webpack loaders should work as well even if not listed here:
 
 - [`babel-loader`](https://www.npmjs.com/package/babel-loader)
 - [`@svgr/webpack`](https://www.npmjs.com/package/@svgr/webpack)
@@ -58,6 +58,7 @@ The following loaders have been tested to work with Turbopack's webpack loader i
 - [`string-replace-loader`](https://www.npmjs.com/package/string-replace-loader)
 - [`raw-loader`](https://www.npmjs.com/package/raw-loader)
 - [`sass-loader`](https://www.npmjs.com/package/sass-loader)
+- [`graphql-tag/loader`](https://www.npmjs.com/package/graphql-tag)
 
 ## Examples
 
@@ -109,6 +110,28 @@ module.exports = {
 }
 ```
 
+For loaders that require configuration options, you can use an object format instead of a string:
+
+```js filename="next.config.js"
+module.exports = {
+  turbopack: {
+    rules: {
+      '*.svg': {
+        loaders: [
+          {
+            loader: '@svgr/webpack',
+            options: {
+              icon: true,
+            },
+          },
+        ],
+        as: '*.js',
+      },
+    },
+  },
+}
+```
+
 > **Good to know**: Prior to Next.js version 13.4.4, `turbo.rules` was named `turbo.loaders` and only accepted file extensions like `.mdx` instead of `*.mdx`.
 
 ### Resolving aliases