Merge branch 'canary' into fix/custom-loader-config

Cargo.toml

@@ -37,11 +37,11 @@ swc_core = { version = "0.90.24", features = [
 testing = { version = "0.35.21" }
 
 # Turbo crates
-turbopack-binding = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-240404.2" }
+turbopack-binding = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-240409.3" }
 # [TODO]: need to refactor embed_directory! macro usages, as well as resolving turbo_tasks::function, macros..
-turbo-tasks = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-240404.2" }
+turbo-tasks = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-240409.3" }
 # [TODO]: need to refactor embed_directory! macro usage in next-core
-turbo-tasks-fs = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-240404.2" }
+turbo-tasks-fs = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-240409.3" }
 
 # General Deps
 

docs/02-app/01-building-your-application/01-routing/06-redirecting.mdx

@@ -215,7 +215,7 @@ export default function Page() {
 
 > **Good to know**:
 >
-> - If you don't need to programatically navigate a user, you should use a [`<Link>`](/docs/app/api-reference/components/link) component.
+> - If you don't need to programmatically navigate a user, you should use a [`<Link>`](/docs/app/api-reference/components/link) component.
 
 <AppOnly>
 

docs/02-app/01-building-your-application/06-optimizing/13-memory-usage.mdx

@@ -36,7 +36,7 @@ If you wish to break before any user code starts, you can pass `--inspect-brk` i
 
 Now, you can use a tool such as Chrome DevTools to connect to the debugging port to record and analyze a snapshot of the heap to see what memory is being retained.
 
-See [how to recored and analyze heap snapshots](https://developer.chrome.com/docs/devtools/memory-problems/heap-snapshots) for more information.
+See [how to record and analyze heap snapshots](https://developer.chrome.com/docs/devtools/memory-problems/heap-snapshots) for more information.
 
 ## Webpack build worker
 

docs/02-app/02-api-reference/05-next-config-js/staleTimes.mdx

@@ -36,7 +36,7 @@ The `static` and `dynamic` properties correspond with the time period (in second
 >
 > - [Loading boundaries](/docs/app/api-reference/file-conventions/loading) are considered reusable for the `static` period defined in this configuration.
 > - This doesn't disable [partial rendering support](/docs/app/building-your-application/routing/linking-and-navigating#4-partial-rendering), **meaning shared layouts won't automatically be refetched every navigation, only the new segment data.**
-> - This doesn't change [back/forward caching](/app/building-your-application/caching#router-cache) behavior to prevent layout shift & to prevent losing the browser scroll position.
+> - This doesn't change [back/forward caching](/docs/app/building-your-application/caching#router-cache) behavior to prevent layout shift & to prevent losing the browser scroll position.
 > - The different properties of this config refer to variable levels of "liveness" and are unrelated to whether the segment itself is opting into static or dynamic rendering. In other words, the current `static` default of 5 minutes suggests that data feels static by virtue of it being revalidated infrequently.
 
 You can learn more about the Client Router Cache [here](/docs/app/building-your-application/caching#router-cache).

docs/02-app/02-api-reference/08-next-cli.mdx

@@ -191,16 +191,6 @@ Options:
   -h, --help                        Displays this message.
 ```
 
-### Profiling
-
-You can enable production profiling for React with the `--profile` flag in `next build`.
-
-```bash filename="Terminal"
-next build --profile
-```
-
-After that, you can use the profiler in the same way as you would in development.
-
 ### Debug
 
 You can enable more verbose build output with the `--debug` flag in `next build`.
@@ -229,6 +219,16 @@ next build --no-mangling
 
 > **Good to know**: This may affect performance and should only be used for debugging purposes.
 
+### Profiling
+
+You can enable production profiling for React with the `--profile` flag in `next build`.
+
+```bash filename="Terminal"
+next build --profile
+```
+
+After that, you can use the profiler in the same way as you would in development.
+
 ## Production
 
 `next start` starts the application in production mode. The application should be compiled with [`next build`](#build) first.
@@ -401,7 +401,7 @@ x"])
   -h, --help                             Displays this message.
 ```
 
-If you have other directories that you would like to lint, you can specfy them using the `--dir` flag:
+If you have other directories that you would like to lint, you can specify them using the `--dir` flag:
 
 ```bash filename="Terminal"
 next lint --dir utils