diff --git a/.github/workflows/benchmark.yml b/.github/workflows/benchmark.yml index 83645d7c3e..fd62da4e90 100644 --- a/.github/workflows/benchmark.yml +++ b/.github/workflows/benchmark.yml @@ -46,7 +46,7 @@ jobs: run: pnpm build - name: Run benchmarks - uses: CodSpeedHQ/action@0b631f8998f2389eb5144632b6f9f8fabd33a86e # v2.4.1 + uses: CodSpeedHQ/action@f11c406b8c87cda176ff341ed4925bc98086f6d1 # v2.4.2 with: run: pnpm vitest bench token: ${{ secrets.CODSPEED_TOKEN }} diff --git a/README.md b/README.md index 9570d902ed..a9df118209 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@

Version Downloads - License + License Website Discord

@@ -120,4 +120,4 @@ If you expect to be using Nuxt 2 beyond the EOL (End of Life) date (June 30, 202 ## ⚖️ License -[MIT](./LICENSE) +[MIT](https://github.com/nuxt/nuxt/tree/main/LICENSE) diff --git a/docs/1.getting-started/10.deployment.md b/docs/1.getting-started/10.deployment.md index 91a4a71cc0..582a24d14a 100644 --- a/docs/1.getting-started/10.deployment.md +++ b/docs/1.getting-started/10.deployment.md @@ -117,10 +117,13 @@ In most cases, Nuxt can work with third-party content that is not generated or c Accordingly, you should make sure that the following options are unchecked / disabled in Cloudflare. Otherwise, unnecessary re-rendering or hydration errors could impact your production application. -1. Speed > Optimization > Auto Minify: Uncheck JavaScript, CSS and HTML -2. Speed > Optimization > Disable "Rocket Loader™" -3. Speed > Optimization > Disable "Mirage" +1. Speed > Optimization > Content Optimization > Auto Minify: Uncheck JavaScript, CSS and HTML +2. Speed > Optimization > Content Optimization > Disable "Rocket Loader™" +3. Speed > Optimization > Image Optimization > Disable "Mirage" 4. Scrape Shield > Disable "Email Address Obfuscation" -5. Scrape Shield > Disable "Server-side Excludes" With these settings, you can be sure that Cloudflare won't inject scripts into your Nuxt application that may cause unwanted side effects. + +::tip +Their location on the Cloudfalre dashboard sometimes changes so don't hesitate to look around. +:: diff --git a/docs/1.getting-started/8.error-handling.md b/docs/1.getting-started/8.error-handling.md index c4b44a438d..3c898508fc 100644 --- a/docs/1.getting-started/8.error-handling.md +++ b/docs/1.getting-started/8.error-handling.md @@ -150,10 +150,10 @@ Read more about `useError` composable. ### `createError` ```ts [TS Signature] -function createError (err: { cause, data, message, name, stack, statusCode, statusMessage, fatal }): Error +function createError (err: string | { cause, data, message, name, stack, statusCode, statusMessage, fatal }): Error ``` -Create an error object with additional metadata. It is usable in both the Vue and Server portions of your app, and is meant to be thrown. +Create an error object with additional metadata. You can pass a string to be set as the error `message` or an object containing error properties. It is usable in both the Vue and Server portions of your app, and is meant to be thrown. If you throw an error created with `createError`: - on server-side, it will trigger a full-screen error page which you can clear with [`clearError`](#clearerror). diff --git a/docs/2.guide/3.going-further/3.modules.md b/docs/2.guide/3.going-further/3.modules.md index 8c354e5e21..7582e90617 100644 --- a/docs/2.guide/3.going-further/3.modules.md +++ b/docs/2.guide/3.going-further/3.modules.md @@ -155,7 +155,7 @@ export default defineNuxtModule({ // Compatibility constraints compatibility: { // Semver version of supported nuxt versions - nuxt: '^3.0.0' + nuxt: '>=3.0.0' } }, // Default configuration options for your module, can also be a function returning those diff --git a/docs/3.api/2.composables/use-async-data.md b/docs/3.api/2.composables/use-async-data.md index 0885af2107..b839fb1d08 100644 --- a/docs/3.api/2.composables/use-async-data.md +++ b/docs/3.api/2.composables/use-async-data.md @@ -18,7 +18,7 @@ Within your pages, components, and plugins you can use useAsyncData to get acces ```vue [pages/index.vue] ``` ::note -`data`, `pending`, `status` and `error` are Vue refs and they should be accessed with `.value` when used within the ` + + +`, 'hello.server.vue') + + expect(normalizeLineEndings(result)).toMatchInlineSnapshot(` + " + + + " + `) + }) + it('expect slot fallback transform to match inline snapshot', async () => { const result = await viteTransform(`