docs: add edge channel

Author: atinux

docs/content/1.get-started/1.installation.md

@@ -31,7 +31,7 @@ export default defineNuxtConfig({
 })
 ```
 
-You can now start using [`<NuxtImg>`](/usage/nuxt-img) and [`<NuxtPicture>`](/usage/nuxt-picture) components in your Nuxt app ✨
+You can now start using [`<NuxtImg>`](/usage/nuxt-img) and [`<NuxtPicture>`](/usage/nuxt-picture) components in your application ✨
 
 ## Configuration
 
@@ -43,7 +43,48 @@ image: {
 }
 ```
 
-See the [image configuration](/get-started/configuration) for all available options and features to customize.
+::callout
+Checkout the [image configuration](/get-started/configuration) for all available options and features to customize.
+::
+
+## Edge Channel
+
+After each commit is merged into the `main` branch of `@nuxt/image` and **passing all tests**, we trigger an automated npm release using Github Actions publishing a [`@nuxt/image-edge`](https://npmjs.com/package/@nuxt/image-edge) package.
+
+You can opt in to use this release channel and avoid waiting for the next release and helping the module by beta testing changes.
+
+The build and publishing method and quality of edge releases are the same as stable ones. The only difference is that you should often check the [GitHub repository](https://github.com/nuxt/image) for updates. There is a slight chance of regressions not being caught during the review process and by the automated tests. Therefore, we internally use this channel to double-check everything before each release.
+
+### Opting into the edge channel
+
+Update `@nuxt/image` dependency inside `package.json`:
+
+```diff [package.json]
+{
+  "devDependencies": {
+-   "@nuxt/image": "^1.0.0"
++   "@nuxt/image": "npm:@nuxt/image-edge@latest"
+  }
+}
+```
+
+Remove lockfile (`package-lock.json`, `yarn.lock`, or `pnpm-lock.yaml`) and reinstall dependencies.
+
+### Opting out from the edge channel
+
+Update `@nuxt/image` dependency inside `package.json`:
+
+```diff [package.json]
+{
+  "devDependencies": {
+-   "@nuxt/image": "npm:@nuxt/image-edge@latest"
++   "@nuxt/image": "^1.0.0"
+  }
+}
+```
+
+Remove lockfile (`package-lock.json`, `yarn.lock`, or `pnpm-lock.yaml`) and reinstall dependencies.
+
 
 ## Troubleshooting
 
@@ -53,25 +94,25 @@ If an error occurs during installation:
 
 - Try to upgrade to latest versions:
 
-::code-group
-  ```bash [pnpm]
-  pnpm up @nuxt/image@rc
-  ```
+  ::code-group
+    ```bash [pnpm]
+    pnpm up @nuxt/image@rc
+    ```
 
-  ```bash [yarn]
-  yarn upgrade @nuxt/image@rc
-  ```
+    ```bash [yarn]
+    yarn upgrade @nuxt/image@rc
+    ```
 
-  ```bash [npm]
-  npm up @nuxt/image@rc
-  ```
-::
+    ```bash [npm]
+    npm up @nuxt/image@rc
+    ```
+  ::
 
 - Try recreating lock-file:
 
-```bash
-npx nuxt@latest upgrade --force
-```
+  ```bash
+  npx nuxt@latest upgrade --force
+  ```
 
 - If there is still an error related to `sharp` and `node-gyp`, it is is probably becase your OS architecture or NodeJS version is not included in pre-built binaries and needs to built from source (for example, this sometimes occurs on Apple M1). Checkout [node-gyp](https://github.com/nodejs/node-gyp#installation) for install requirements.