Merge branch 'canary' into zt/upgrade-react

.github/workflows/issue_validator.yml

@@ -18,7 +18,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Nissuer
-        uses: balazsorban44/nissuer@1.3.5
+        uses: balazsorban44/nissuer@1.4.0
         with:
           label-area-prefix: 'area:'
           label-area-section: 'Which area\(s\) are affected\? \(Select all that apply\)(.*)### Additional context'
@@ -32,3 +32,4 @@ jobs:
           reproduction-hosts: 'github.com,codesandbox.io'
           reproduction-link-section: '### Link to the code that reproduces this issue(.*)### To Reproduce'
           reproduction-invalid-label: 'invalid link'
+          reproduction-issue-labels: 'template: bug'

Cargo.toml

@@ -45,11 +45,11 @@ swc_core = { version = "0.83.12", features = [
 testing = { version = "0.34.1" }
 
 # Turbo crates
-turbopack-binding = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230917.1" }
+turbopack-binding = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230918.2" }
 # [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-230917.1" }
+turbo-tasks = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230918.2" }
 # [TODO]: need to refactor embed_directory! macro usage in next-core
-turbo-tasks-fs = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230917.1" }
+turbo-tasks-fs = { git = "https://github.com/vercel/turbo.git", tag = "turbopack-230918.2" }
 
 # General Deps
 

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

@@ -7,11 +7,13 @@ description:
 
 Some packages can export hundreds or thousands of modules, which can cause performance issues in development and production.
 
-Adding a package to `optimizePackageImports` will only load the modules you are actually using, while still giving you the convenience of writing import statements with many named exports.
+Adding a package to `experimental.optimizePackageImports` will only load the modules you are actually using, while still giving you the convenience of writing import statements with many named exports.
 
 ```js filename="next.config.js"
 module.exports = {
-  optimizePackageImports: ['package-name'],
+  experimental: {
+    optimizePackageImports: ['package-name'],
+  },
 }
 ```
 

docs/03-pages/01-building-your-application/06-configuring/12-error-handling.mdx

@@ -7,7 +7,7 @@ This documentation explains how you can handle development, server-side, and cli
 
 ## Handling Errors in Development
 
-When there is a runtime error during the development phase of your Next.js application, you will encounter an **overlay**. It is a modal that covers the webpage. It is **only** visible when the development server runs using `next dev` via `pnpm dev`, `npm run dev`, `yarn dev`, or `bun run dev` and will not be shown in production. Fixing the error will automatically dismiss the overlay.
+When there is a runtime error during the development phase of your Next.js application, you will encounter an **overlay**. It is a modal that covers the webpage. It is **only** visible when the development server runs using `next dev` via `pnpm dev`, `npm run dev`, `yarn dev`, or `bun dev` and will not be shown in production. Fixing the error will automatically dismiss the overlay.
 
 Here is an example of an overlay:
 

examples/with-fauna/package.json

@@ -10,7 +10,7 @@
     "classnames": "2.3.1",
     "date-fns": "2.28.0",
     "faunadb": "4.5.4",
-    "graphql": "16.5.0",
+    "graphql": "16.8.1",
     "graphql-request": "4.3.0",
     "next": "latest",
     "react": "18.1.0",