From 1586f991e3005be3e7586de543271ef03ae7df78 Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Wed, 27 Jul 2022 16:06:46 +0200
Subject: [PATCH 01/20] Fix exports in propTypes.js to fix website build

---
 packages/@uppy/react/src/propTypes.js | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/packages/@uppy/react/src/propTypes.js b/packages/@uppy/react/src/propTypes.js
index b06db10d20..e744a3dd1d 100644
--- a/packages/@uppy/react/src/propTypes.js
+++ b/packages/@uppy/react/src/propTypes.js
@@ -55,4 +55,7 @@ export {
   uppy,
   locale,
   dashboard,
+  plugins,
+  metaFields,
+  cssSize,
 }

From 163e64b35f7d6369d7eb5f902835ec99437a0960 Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Wed, 27 Jul 2022 16:10:38 +0200
Subject: [PATCH 02/20] Add migration guide for Uppy 3.x and Companion 4.x

---
 website/src/docs/migration-guides.md | 63 +++++++++++++++++++++++++++-
 1 file changed, 61 insertions(+), 2 deletions(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 0129754e36..5bc4c22018 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -8,7 +8,66 @@ category: "Docs"
 
 These cover all the major Uppy versions and how to migrate to them.
 
-## Migrate to 2.0.0
+## Migrate from Uppy 2.x to 3.x
+
+### Uppy is pure ESM
+
+Following the footsteps of many packages, we now only ship [ECMAScript Modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules) (ESM). Uppy can’t be `require()`’d from CommonJS.
+
+Before Uppy 3.x, you could use `require` or `import` as we shipped CommonJS:
+
+<!-- eslint-disable no-restricted-globals -->
+
+```js
+const Uppy = require('@uppy/core')
+const Dashboard = require('@uppy/dashboard')
+```
+
+Now Uppy can only be `import`’ed:
+
+```js
+import Uppy from '@uppy/core'
+import Dashboard from '@uppy/dashboard'
+```
+
+Refer to the [Pure ESM package](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c) gist for added information and help.
+
+## Migrate from Companion 3.x to 4.x
+
+### Minimum required Node.js version is v14.19.0
+
+Aligning with the Node.js [Long Term Support (LTS) schedule](https://nodejs.org/en/about/releases/) and to use modern syntax features.
+
+### `companion.app()` returns `{ app, emitter }` instead of `app`
+
+Companion 3.x provides the emitter as `companionEmitter` on `app`. As of 4.x, an object is returned with `app` (express middleware) and `emitter` (event emitter). This provides more flexibility in the future and follows best practices.
+
+### Removed compatibility for legacy Custom Provider implementations
+
+[Custom Provider](https://uppy.io/docs/companion/#Adding-custom-providers) implementations must use the Promise API, instead of the callback API.
+
+### Default to no ACL for AWS S3
+
+Default to no [ACL](https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html) for S3 uploads. Before the default was `public-read` but AWS now discourages ACLs. The environment variable `COMPANION_AWS_DISABLE_ACL` is also removed, instead Companion only uses `COMPANION_AWS_ACL`.
+
+### `protocol` sent from Uppy in any `get` request is now required (before it would default to Multipart).
+
+If you use any official Uppy plugins, then no migration is needed. For custom plugins that talk to Companion, make to send along the `protocol` header with a value of `multipart`, `s3Multipart`, or `tus`.
+
+### `emitSuccess` and `emitError` are now private methods on the `Uploader` class.
+
+It’s unlikely you’re using this, but it’s technically a breaking change.
+In general, don’t depend on implicitly internal methods, use exposed APIs instead.
+
+### Removed `chunkSize` backwards compatibility for AWS S3 Multipart
+
+`chunkSize` option will now be used as `partSize` in AWS multipart. Before only valid values would be respected. Invalid values would be ignored. Now any value will be passed on to the AWS SDK, possibly throwing an error on invalid values.
+
+### Removed backwards compatibility for `/metrics` endpoint
+
+TODO @mifi
+
+## Migrate from Uppy 1.x to 2.x
 
 ### New bundle requires manual polyfilling
 
@@ -247,7 +306,7 @@ Uppy 1.0 will continue to receive bug fixes for three more months (until <time d
 
 We hope you’ll waste no time in taking Uppy 2.0 out for a walk. When you do, please let us know what you thought of it on [Reddit](https://www.reddit.com/r/javascript/comments/penbr7/uppy_file_uploader_20_smaller_and_faster_modular/), [HN](https://news.ycombinator.com/item?id=28359287), ProductHunt, or [Twitter](https://twitter.com/uppy_io/status/1432399270846603264). We’re howling at the moon to hear from you!
 
-## Migrating Companion v1 to v2
+## Migrate from Companion 1.x to 2.x
 
 ### Prerequisite
 

From ee1143bce651094996c983448aa22cab92d12ec2 Mon Sep 17 00:00:00 2001
From: Merlijn Vos <merlijn@soverin.net>
Date: Wed, 3 Aug 2022 11:57:47 +0200
Subject: [PATCH 03/20] Apply suggestions from code review

Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
---
 website/src/docs/migration-guides.md | 34 ++++++++++++----------------
 1 file changed, 14 insertions(+), 20 deletions(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 5bc4c22018..16f9f86410 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -12,39 +12,33 @@ These cover all the major Uppy versions and how to migrate to them.
 
 ### Uppy is pure ESM
 
-Following the footsteps of many packages, we now only ship [ECMAScript Modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules) (ESM). Uppy can’t be `require()`’d from CommonJS.
+Following the footsteps of many packages, we now only ship Uppy core and its plugins as
+[ECMAScript Modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules) (ESM).
+On Uppy 2.x, we were shipping CommonJS.
 
-Before Uppy 3.x, you could use `require` or `import` as we shipped CommonJS:
+If are already using ESM yourself, or are using the CDN builds, nothing changes for you!
 
-<!-- eslint-disable no-restricted-globals -->
-
-```js
-const Uppy = require('@uppy/core')
-const Dashboard = require('@uppy/dashboard')
-```
-
-Now Uppy can only be `import`’ed:
-
-```js
-import Uppy from '@uppy/core'
-import Dashboard from '@uppy/dashboard'
-```
-
-Refer to the [Pure ESM package](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c) gist for added information and help.
+If you are using CommonJS, you might need to add some tooling for everything to work, or you might
+want to refactor your codebase to ESM – refer to
+the [Pure ESM package](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c)
+gist for additional information and help on how to do that.
 
 ## Migrate from Companion 3.x to 4.x
 
-### Minimum required Node.js version is v14.19.0
+### Minimum required Node.js version is v14.20.0
 
 Aligning with the Node.js [Long Term Support (LTS) schedule](https://nodejs.org/en/about/releases/) and to use modern syntax features.
 
 ### `companion.app()` returns `{ app, emitter }` instead of `app`
 
-Companion 3.x provides the emitter as `companionEmitter` on `app`. As of 4.x, an object is returned with `app` (express middleware) and `emitter` (event emitter). This provides more flexibility in the future and follows best practices.
+Companion 3.x provides the emitter as `companionEmitter` on `app`. As of 4.x, an object is returned
+with an `app` property (express middleware) and an `emitter` property (event emitter). This
+provides more flexibility in the future and follows best practices.
 
 ### Removed compatibility for legacy Custom Provider implementations
 
-[Custom Provider](https://uppy.io/docs/companion/#Adding-custom-providers) implementations must use the Promise API, instead of the callback API.
+[Custom Provider](https://uppy.io/docs/companion/#Adding-custom-providers)
+implementations must use the Promise API. The callback API is no longer supported.
 
 ### Default to no ACL for AWS S3
 

From d774051fde1aa4a8fb64213579edca679af9403c Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Wed, 3 Aug 2022 12:13:48 +0200
Subject: [PATCH 04/20] Add Robodog section

---
 website/src/docs/migration-guides.md | 19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 164481abf1..921c280ba2 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -21,7 +21,24 @@ If are already using ESM yourself, or are using the CDN builds, nothing changes
 If you are using CommonJS, you might need to add some tooling for everything to work, or you might
 want to refactor your codebase to ESM – refer to
 the [Pure ESM package](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c)
-gist for additional information and help on how to do that.
+gist for added information and help on how to do that.
+
+### Robodog is deprecated
+
+Uppy is flexible and extensible through plugins. But the integration code could sometimes be daunting. This is what brought [Robodog](/docs/robodog/) to life. An alternative with the same features, but with a more ergonomic and minimal API.
+
+But, it didn’t come with its own set of new problems:
+
+* It tries to do the exact same, but it looks like a different product
+* It’s confusing for users whether they want to use Robodog or Uppy directly.
+* Documentation is scarce, and the trade offs are unclear
+* It’s not marketed, you need to stumble on it in the docs.
+* Extra maintenance burden
+* Extra hosting effort and costs
+
+This has now led us to deprecating Robodog and embrace Uppy for its strong suits; modularity and flexibility. At the same time, we also introduced something to take away some repetitive integration code: [`@uppy/remote-sources`](/docs/remote-sources).
+
+To migrate from Robodog to Uppy plugins, go through the [list of plugins](/docs/plugins/) and install and use the ones you need.
 
 ## Migrate from Companion 3.x to 4.x
 

From 37cb0303833d39dd0f9b1581ff54fa2b38688fa8 Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Wed, 3 Aug 2022 17:31:34 +0200
Subject: [PATCH 05/20] Add breaking changes from todos

---
 website/src/docs/migration-guides.md | 40 ++++++++++++++++++++++++++++
 1 file changed, 40 insertions(+)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 921c280ba2..7f7220da23 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -40,6 +40,46 @@ This has now led us to deprecating Robodog and embrace Uppy for its strong suits
 
 To migrate from Robodog to Uppy plugins, go through the [list of plugins](/docs/plugins/) and install and use the ones you need.
 
+### Smaller breaking changes
+
+We also made a couple of changes which are technically breaking, but unlikely to be so for most users (making something internal private, for instance).
+
+#### `@uppy/core`
+
+* Remove `AggregateError` polyfill
+  * reason: [should be polyfilled by the user](https://github.com/transloadit/uppy/pull/3532#discussion_r818602636)
+  * migrate: install a `AggregateError` polyfill or use `core-js`
+* Remove `reset()` method
+  * reason: it’s a duplicate of `cancelAll`, but with a less intention revealing name
+  * migrate: use `cancelAll`
+* Remove backwards compatible exports (static properties on `Uppy`). Exports, such as `debugLogger`, used to also be accesible on the `Uppy` export. This has now been removed.
+  * reason: transition to ESM
+  * migrate: import the `Uppy` class by default and/or use named exports for everything else.
+
+#### `@uppy/aws-s3-multipart`
+
+* Remove `client` getter and setter.
+  * reason: internal usage only
+  * migrate: use exposed options only
+
+#### `@uppy/react`
+
+* Don’t expose `validProps` on the exported components.
+  * reason: internal usage only
+  * migrate: use exposed options only
+
+#### `@uppy/store-redux`
+
+* Remove backwards compatible exports (static properties on `ReduxStore`). Exports, such as `reducer`, used to also be accesible on the `ReduxStore` export. This has now been removed.
+  * reason: transition to ESM
+  * migrate: use named imports
+
+#### `@uppy/thumbnail-generator`
+
+* Remove `rotateImage`, `protect`, and `canvasToBlob` from plugin prototype.
+  * reason: internal usage only
+  * migrate: use exposed options only
+
 ## Migrate from Companion 3.x to 4.x
 
 ### Minimum required Node.js version is v14.20.0

From 0f7cc66c427d5333133f08744de1b64c4dd6b57c Mon Sep 17 00:00:00 2001
From: Merlijn Vos <merlijn@soverin.net>
Date: Wed, 3 Aug 2022 17:38:10 +0200
Subject: [PATCH 06/20] Update website/src/docs/migration-guides.md

Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
---
 website/src/docs/migration-guides.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 7f7220da23..eaf17de492 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -46,14 +46,14 @@ We also made a couple of changes which are technically breaking, but unlikely to
 
 #### `@uppy/core`
 
-* Remove `AggregateError` polyfill
-  * reason: [should be polyfilled by the user](https://github.com/transloadit/uppy/pull/3532#discussion_r818602636)
-  * migrate: install a `AggregateError` polyfill or use `core-js`
-* Remove `reset()` method
-  * reason: it’s a duplicate of `cancelAll`, but with a less intention revealing name
-  * migrate: use `cancelAll`
+* Remove `AggregateError` polyfill.
+  * reason: it's supported by most modern browsers, it [can be polyfilled by the user](https://github.com/transloadit/uppy/pull/3532#discussion_r818602636).
+  * migrate: install a `AggregateError` polyfill or use `core-js`.
+* Remove `reset()` method.
+  * reason: it’s a duplicate of `cancelAll`, but with a less intention revealing name.
+  * migrate: use `cancelAll`.
 * Remove backwards compatible exports (static properties on `Uppy`). Exports, such as `debugLogger`, used to also be accesible on the `Uppy` export. This has now been removed.
-  * reason: transition to ESM
+  * reason: transition to ESM.
   * migrate: import the `Uppy` class by default and/or use named exports for everything else.
 
 #### `@uppy/aws-s3-multipart`

From 40ddfc2c59ff5e6c572f23465600f90ee265890d Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Wed, 3 Aug 2022 17:40:50 +0200
Subject: [PATCH 07/20] Small tweaks

---
 website/src/docs/migration-guides.md | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index eaf17de492..47c78782ca 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -31,6 +31,7 @@ But, it didn’t come with its own set of new problems:
 
 * It tries to do the exact same, but it looks like a different product
 * It’s confusing for users whether they want to use Robodog or Uppy directly.
+* Robodog is more ergonomic because it’s limited. When you hit such a limit, you need to refactor everything to Uppy with plugins.
 * Documentation is scarce, and the trade offs are unclear
 * It’s not marketed, you need to stumble on it in the docs.
 * Extra maintenance burden
@@ -47,7 +48,7 @@ We also made a couple of changes which are technically breaking, but unlikely to
 #### `@uppy/core`
 
 * Remove `AggregateError` polyfill.
-  * reason: it's supported by most modern browsers, it [can be polyfilled by the user](https://github.com/transloadit/uppy/pull/3532#discussion_r818602636).
+  * reason: it’s supported by most modern browsers and [can be polyfilled by the user](https://github.com/transloadit/uppy/pull/3532#discussion_r818602636) if needed.
   * migrate: install a `AggregateError` polyfill or use `core-js`.
 * Remove `reset()` method.
   * reason: it’s a duplicate of `cancelAll`, but with a less intention revealing name.
@@ -59,26 +60,26 @@ We also made a couple of changes which are technically breaking, but unlikely to
 #### `@uppy/aws-s3-multipart`
 
 * Remove `client` getter and setter.
-  * reason: internal usage only
-  * migrate: use exposed options only
+  * reason: internal usage only.
+  * migrate: use exposed options only.
 
 #### `@uppy/react`
 
 * Don’t expose `validProps` on the exported components.
-  * reason: internal usage only
-  * migrate: use exposed options only
+  * reason: internal usage only.
+  * migrate: use exposed options only.
 
 #### `@uppy/store-redux`
 
 * Remove backwards compatible exports (static properties on `ReduxStore`). Exports, such as `reducer`, used to also be accesible on the `ReduxStore` export. This has now been removed.
-  * reason: transition to ESM
-  * migrate: use named imports
+  * reason: transition to ESM.
+  * migrate: use named imports.
 
 #### `@uppy/thumbnail-generator`
 
 * Remove `rotateImage`, `protect`, and `canvasToBlob` from plugin prototype.
-  * reason: internal usage only
-  * migrate: use exposed options only
+  * reason: internal usage only.
+  * migrate: use exposed options only.
 
 ## Migrate from Companion 3.x to 4.x
 

From 9cf9a13881cdced6c2b9236076e57033b2d60630 Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Wed, 3 Aug 2022 17:46:33 +0200
Subject: [PATCH 08/20] Add section about s3 option changes

---
 website/src/docs/migration-guides.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 47c78782ca..99e062f0ad 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -93,6 +93,14 @@ Companion 3.x provides the emitter as `companionEmitter` on `app`. As of 4.x, an
 with an `app` property (express middleware) and an `emitter` property (event emitter). This
 provides more flexibility in the future and follows best practices.
 
+### Removed `searchProviders` wrapper object inside `providerOptions`
+
+To use [`@uppy/unsplash`](/docs/unsplash), you had to configure Unsplash in Companion inside `providerOptions.searchProviders`. This is redundant, Unsplash is a provider as well so we removed the wrapper object.
+
+### Moved the `s3` options out of `providerOptions`
+
+To use AWS S3 for storage, you configured the `s3` object inside `providerOptions`. But as S3 is not a provider but a destination. To avoid confusion we moved the `s3` settings to the root settings object.
+
 ### Removed compatibility for legacy Custom Provider implementations
 
 [Custom Provider](https://uppy.io/docs/companion/#Adding-custom-providers)

From 78387c932b9c07bc92bd94b15584fba13b79ef30 Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Wed, 3 Aug 2022 17:52:56 +0200
Subject: [PATCH 09/20] Add aws-s3-multipart changes

---
 website/src/docs/migration-guides.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 99e062f0ad..9e48854236 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -43,8 +43,6 @@ To migrate from Robodog to Uppy plugins, go through the [list of plugins](/docs/
 
 ### Smaller breaking changes
 
-We also made a couple of changes which are technically breaking, but unlikely to be so for most users (making something internal private, for instance).
-
 #### `@uppy/core`
 
 * Remove `AggregateError` polyfill.
@@ -59,6 +57,9 @@ We also made a couple of changes which are technically breaking, but unlikely to
 
 #### `@uppy/aws-s3-multipart`
 
+* Make `headers` inside the return value of [`prepareUploadParts`](/docs/aws-s3-multipart/#prepareUploadParts-file-partData) part-indexed too.
+  * reason: allow custom headers to be set per part. See this [issue](https://github.com/transloadit/uppy/issues/3881) for details.
+  * migrate: make headers part indexed like `presignedUrls`: `{ "headers": { "1": { "Content-MD5": "foo" } }}`.
 * Remove `client` getter and setter.
   * reason: internal usage only.
   * migrate: use exposed options only.

From 83e37250da30f1d95426953646b3249438007a76 Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Thu, 4 Aug 2022 12:22:19 +0200
Subject: [PATCH 10/20] Add Robodog migration guide

---
 website/src/docs/migration-guides.md | 95 +++++++++++++++++++++++-----
 1 file changed, 80 insertions(+), 15 deletions(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 9e48854236..024dd652a3 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -8,6 +8,85 @@ category: "Docs"
 
 These cover all the major Uppy versions and how to migrate to them.
 
+## Migrate from Robodog to Uppy plugins
+
+Uppy is flexible and extensible through plugins. But the integration code could sometimes be daunting. This is what brought [Robodog](/docs/robodog/) to life. An alternative with the same features, but with a more ergonomic and minimal API.
+
+But, it didn’t come with its own set of new problems:
+
+* It tries to do the exact same, but it looks like a different product
+* It’s confusing for users whether they want to use Robodog or Uppy directly.
+* Robodog is more ergonomic because it’s limited. When you hit such a limit, you need to refactor everything to Uppy with plugins.
+* Documentation is scarce, and the trade offs are unclear
+* It’s not marketed, you need to stumble on it in the docs.
+* Extra maintenance burden
+* Extra hosting effort and costs
+
+This has now led us to deprecating Robodog and embrace Uppy for its strong suits; modularity and flexibility. At the same time, we also introduced something to take away some repetitive integration code: [`@uppy/remote-sources`](/docs/remote-sources).
+
+To mimic the Robodog implementation with all its features, you can use the code snippet below. But chances are Robodog did more than you need so feel free to remove things or go through the [list of plugins](/docs/plugins/) and install and use the ones you need.
+
+```js
+import Uppy from '@uppy/core'
+import Dashboard from '@uppy/dashboard'
+import RemoteSources from '@uppy/remote-sources'
+import Webcam from '@uppy/webcam'
+import ScreenCapture from '@uppy/screen-capture'
+import GoldenRetriever from '@uppy/golden-retriever'
+import ImageEditor from '@uppy/image-editor'
+import Audio from '@uppy/audio'
+import Transloadit from '@uppy/transloadit'
+
+import '@uppy/core/dist/style.css'
+import '@uppy/dashboard/dist/style.css'
+import '@uppy/audio/dist/style.css'
+import '@uppy/screen-capture/dist/style.css'
+import '@uppy/image-editor/dist/style.css'
+
+const {
+  COMPANION_URL,
+  COMPANION_ALLOWED_HOSTS,
+  TRANSLOADIT_SERVICE_URL,
+  TRANSLOADIT_KEY,
+  TRANSLOADIT_SECRET,
+} = import.meta.env
+
+new Uppy()
+  .use(Dashboard, {
+    inline: true,
+    target: '#app',
+    showProgressDetails: true,
+    proudlyDisplayPoweredByUppy: true,
+  })
+  .use(RemoteSources, {
+    companionUrl: COMPANION_URL,
+    companionAllowedHosts: COMPANION_ALLOWED_HOSTS,
+  })
+  .use(Webcam, {
+    target: Dashboard,
+    showVideoSourceDropdown: true,
+    showRecordingLength: true,
+  })
+  .use(Audio, {
+    target: Dashboard,
+    showRecordingLength: true,
+  })
+  .use(ScreenCapture, { target: Dashboard })
+  .use(ImageEditor, { target: Dashboard })
+  .use(Transloadit, {
+    service: TRANSLOADIT_SERVICE_URL,
+    async getAssemblyOptions (file) {
+      // This is where you configure your auth key, auth secret, and template ID
+      // https://uppy.io/docs/transloadit/#getAssemblyOptions-file
+      //
+      // It is important to set the secret in production:
+      // https://transloadit.com/docs/topics/signature-authentication/
+      const response = await fetch('/some-endpoint')
+      return response.json()
+    },
+  })
+```
+
 ## Migrate from Uppy 2.x to 3.x
 
 ### Uppy is pure ESM
@@ -25,21 +104,7 @@ gist for added information and help on how to do that.
 
 ### Robodog is deprecated
 
-Uppy is flexible and extensible through plugins. But the integration code could sometimes be daunting. This is what brought [Robodog](/docs/robodog/) to life. An alternative with the same features, but with a more ergonomic and minimal API.
-
-But, it didn’t come with its own set of new problems:
-
-* It tries to do the exact same, but it looks like a different product
-* It’s confusing for users whether they want to use Robodog or Uppy directly.
-* Robodog is more ergonomic because it’s limited. When you hit such a limit, you need to refactor everything to Uppy with plugins.
-* Documentation is scarce, and the trade offs are unclear
-* It’s not marketed, you need to stumble on it in the docs.
-* Extra maintenance burden
-* Extra hosting effort and costs
-
-This has now led us to deprecating Robodog and embrace Uppy for its strong suits; modularity and flexibility. At the same time, we also introduced something to take away some repetitive integration code: [`@uppy/remote-sources`](/docs/remote-sources).
-
-To migrate from Robodog to Uppy plugins, go through the [list of plugins](/docs/plugins/) and install and use the ones you need.
+See the [Robodog migration guide](#Migrate-from-Robodog-to-Uppy-plugins).
 
 ### Smaller breaking changes
 

From ebedbcc7135d4d946a0bf34fc3314aa15e22933a Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Thu, 4 Aug 2022 12:29:10 +0200
Subject: [PATCH 11/20] Remove unused code in example

---
 website/src/docs/migration-guides.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 024dd652a3..96665ac3c8 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -47,8 +47,6 @@ const {
   COMPANION_URL,
   COMPANION_ALLOWED_HOSTS,
   TRANSLOADIT_SERVICE_URL,
-  TRANSLOADIT_KEY,
-  TRANSLOADIT_SECRET,
 } = import.meta.env
 
 new Uppy()

From 38c48ac0e958601a974e207d2dbe5edd1562a406 Mon Sep 17 00:00:00 2001
From: Merlijn Vos <merlijn@soverin.net>
Date: Thu, 4 Aug 2022 15:46:04 +0200
Subject: [PATCH 12/20] Add section for metrics endpoint

Co-authored-by: Mikael Finstad <finstaden@gmail.com>
---
 website/src/docs/migration-guides.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 96665ac3c8..6e417b0641 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -189,7 +189,9 @@ In general, don’t depend on implicitly internal methods, use exposed APIs inst
 
 ### Removed backwards compatibility for `/metrics` endpoint
 
-TODO @mifi
+The `metrics` option is a boolean flag to tell Companion whether to provide an endpoint `/metrics` with Prometheus metrics. Metrics will now always be served under `options.server.path`. Before v4.x, it would always be served under the root.
+
+For example: if `{ options: { metrics: true, server: { path: '/companion' }}}`, metrics will now be served under `/companion/metrics`. In v3.x, the metrics would be served under `/metrics`.
 
 ## Migrate from Uppy 1.x to 2.x
 

From 923a503dcaaa177b3b7c954a807652662efd344e Mon Sep 17 00:00:00 2001
From: Merlijn Vos <merlijn@soverin.net>
Date: Mon, 8 Aug 2022 11:14:27 +0200
Subject: [PATCH 13/20] Update website/src/docs/migration-guides.md

Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
---
 website/src/docs/migration-guides.md | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 6e417b0641..d1c099c6ae 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -14,13 +14,10 @@ Uppy is flexible and extensible through plugins. But the integration code could
 
 But, it didn’t come with its own set of new problems:
 
-* It tries to do the exact same, but it looks like a different product
+* It tries to do the exact same, but it looks like a different product.
 * It’s confusing for users whether they want to use Robodog or Uppy directly.
-* Robodog is more ergonomic because it’s limited. When you hit such a limit, you need to refactor everything to Uppy with plugins.
-* Documentation is scarce, and the trade offs are unclear
-* It’s not marketed, you need to stumble on it in the docs.
-* Extra maintenance burden
-* Extra hosting effort and costs
+* Robodog is more ergonomic because it’s limited. When you hit such a limit, you
+  need to refactor everything to Uppy with plugins.
 
 This has now led us to deprecating Robodog and embrace Uppy for its strong suits; modularity and flexibility. At the same time, we also introduced something to take away some repetitive integration code: [`@uppy/remote-sources`](/docs/remote-sources).
 

From a1be411531f75d1f66602b561f27bf6a43d7e811 Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Mon, 22 Aug 2022 15:07:44 +0200
Subject: [PATCH 14/20] Add missing @uppy/transloadit breaking changes

---
 website/src/docs/migration-guides.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index d1c099c6ae..83fa22fd47 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -115,6 +115,22 @@ See the [Robodog migration guide](#Migrate-from-Robodog-to-Uppy-plugins).
   * reason: transition to ESM.
   * migrate: import the `Uppy` class by default and/or use named exports for everything else.
 
+#### `@uppy/transloadit`
+
+Remove export of `ALLOWED_COMPANION_PATTERN`, `COMPANION`, and `COMPANION_PATTERN` in favor of `COMPANION_URL` and `COMPANION_ALLOWED_HOSTS`. This is to have more intention revealing names, `COMPANION` sounds like the Companion instance, `COMPANION_URL` makes it more clear that it’s a URL.
+
+These are properties can now be imported and used for remote sources plugins when using Transloadit:
+
+```js
+import { COMPANION_URL, COMPANION_ALLOWED_HOSTS } from '@uppy/transloadit'
+
+// ...
+uppy.use(Dropbox, {
+  companionUrl: COMPANION_URL,
+  companionAllowedHosts: COMPANION_ALLOWED_HOSTS,
+})
+```
+
 #### `@uppy/aws-s3-multipart`
 
 * Make `headers` inside the return value of [`prepareUploadParts`](/docs/aws-s3-multipart/#prepareUploadParts-file-partData) part-indexed too.

From 049e10d3422877bd60f11f437072ad77ffcb0f8f Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Mon, 22 Aug 2022 15:15:15 +0200
Subject: [PATCH 15/20] Add `validateRestrictions` breaking change

---
 website/src/docs/migration-guides.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 83fa22fd47..8d90f6371d 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -111,9 +111,12 @@ See the [Robodog migration guide](#Migrate-from-Robodog-to-Uppy-plugins).
 * Remove `reset()` method.
   * reason: it’s a duplicate of `cancelAll`, but with a less intention revealing name.
   * migrate: use `cancelAll`.
-* Remove backwards compatible exports (static properties on `Uppy`). Exports, such as `debugLogger`, used to also be accesible on the `Uppy` export. This has now been removed.
+* Remove backwards compatible exports (static properties on `Uppy`). Exports, such as `debugLogger`, used to also be accessible on the `Uppy` export. This has now been removed.
   * reason: transition to ESM.
   * migrate: import the `Uppy` class by default and/or use named exports for everything else.
+* `uppy.validateRestrictions()` now returns a `RestrictionError`, which is an extended `Error` class, instead of `{ result: false, reason: err.message }`.
+  * reason: best practises, this method should return `null` or an error instead of trying to mimic an error with `result: false`.
+  * migrate: check the return value, if it’s defined you have an error, otherwise all went well. Note that the error is `return`’ed, it’s not `throw`’n.
 
 #### `@uppy/transloadit`
 

From be6d816aa947ad1e29e130a9ae346d5b6240443f Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Mon, 22 Aug 2022 15:28:36 +0200
Subject: [PATCH 16/20] Small rewrites + improved formatting

---
 website/src/docs/migration-guides.md | 76 ++++++++++++++++------------
 1 file changed, 45 insertions(+), 31 deletions(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 8d90f6371d..5389791c7e 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -101,22 +101,31 @@ gist for added information and help on how to do that.
 
 See the [Robodog migration guide](#Migrate-from-Robodog-to-Uppy-plugins).
 
-### Smaller breaking changes
-
-#### `@uppy/core`
-
-* Remove `AggregateError` polyfill.
-  * reason: it’s supported by most modern browsers and [can be polyfilled by the user](https://github.com/transloadit/uppy/pull/3532#discussion_r818602636) if needed.
-  * migrate: install a `AggregateError` polyfill or use `core-js`.
-* Remove `reset()` method.
-  * reason: it’s a duplicate of `cancelAll`, but with a less intention revealing name.
-  * migrate: use `cancelAll`.
-* Remove backwards compatible exports (static properties on `Uppy`). Exports, such as `debugLogger`, used to also be accessible on the `Uppy` export. This has now been removed.
-  * reason: transition to ESM.
-  * migrate: import the `Uppy` class by default and/or use named exports for everything else.
-* `uppy.validateRestrictions()` now returns a `RestrictionError`, which is an extended `Error` class, instead of `{ result: false, reason: err.message }`.
-  * reason: best practises, this method should return `null` or an error instead of trying to mimic an error with `result: false`.
-  * migrate: check the return value, if it’s defined you have an error, otherwise all went well. Note that the error is `return`’ed, it’s not `throw`’n.
+### `@uppy/core`
+
+#### Remove `AggregateError` polyfill.
+
+It’s supported by most modern browsers and [can be polyfilled by the user](https://github.com/transloadit/uppy/pull/3532#discussion_r818602636) if needed.
+
+To migrate: install a `AggregateError` polyfill or use `core-js`.
+
+#### Remove `reset()` method.
+
+It’s a duplicate of `cancelAll`, but with a less intention revealing name.
+
+To migrate: use `cancelAll`.
+
+#### Remove backwards compatible exports (static properties on `Uppy`)\`
+
+`Uppy`, `UIPlugin`, `BasePlugin`, and `debugLogger` used to also be accessible on the `Uppy` export. This has now been removed due to the transition to ESM.
+
+To migrate: import the `Uppy` class by default and/or use named exports for everything else.
+
+#### `uppy.validateRestrictions()` now returns a `RestrictionError`
+
+This method used to return `{ result: false, reason: err.message }`, but that felt strange as it tries to mimic an error. Instead it now return a `RestrictionError`, which is extended `Error` class.
+
+To migrate: check the return value, if it’s defined you have an error, otherwise all went well. Note that the error is `return`’ed, it’s not `throw`’n, so you don’t have to `catch` it.
 
 #### `@uppy/transloadit`
 
@@ -136,30 +145,35 @@ uppy.use(Dropbox, {
 
 #### `@uppy/aws-s3-multipart`
 
-* Make `headers` inside the return value of [`prepareUploadParts`](/docs/aws-s3-multipart/#prepareUploadParts-file-partData) part-indexed too.
-  * reason: allow custom headers to be set per part. See this [issue](https://github.com/transloadit/uppy/issues/3881) for details.
-  * migrate: make headers part indexed like `presignedUrls`: `{ "headers": { "1": { "Content-MD5": "foo" } }}`.
-* Remove `client` getter and setter.
-  * reason: internal usage only.
-  * migrate: use exposed options only.
+##### Make `headers` inside the return value of [`prepareUploadParts`](/docs/aws-s3-multipart/#prepareUploadParts-file-partData) part-indexed too.
+
+This is to allow custom headers to be set per part. See this [issue](https://github.com/transloadit/uppy/issues/3881) for details.
+
+To migrate: make headers part indexed like `presignedUrls`: `{ "headers": { "1": { "Content-MD5": "foo" } }}`.
+
+##### Remove `client` getter and setter.
+
+It’s internal usage only.
+
+To migrate: use exposed options only.
 
 #### `@uppy/react`
 
-* Don’t expose `validProps` on the exported components.
-  * reason: internal usage only.
-  * migrate: use exposed options only.
+Don’t expose `validProps` on the exported components. They are internal usage only.
+
+To migrate: use exposed options only.
 
 #### `@uppy/store-redux`
 
-* Remove backwards compatible exports (static properties on `ReduxStore`). Exports, such as `reducer`, used to also be accesible on the `ReduxStore` export. This has now been removed.
-  * reason: transition to ESM.
-  * migrate: use named imports.
+Remove backwards compatible exports (static properties on `ReduxStore`). Exports, such as `reducer`, used to also be accessible on the `ReduxStore` export. This has now been removed due to the transition to ESM.
+
+To migrate: use named imports.
 
 #### `@uppy/thumbnail-generator`
 
-* Remove `rotateImage`, `protect`, and `canvasToBlob` from plugin prototype.
-  * reason: internal usage only.
-  * migrate: use exposed options only.
+Remove `rotateImage`, `protect`, and `canvasToBlob` from the plugin prototype. They are internal usage only.
+
+To migrate: use exposed options only.
 
 ## Migrate from Companion 3.x to 4.x
 

From e757341bfd071bce17f55d58beb9bcb0dba7e6e0 Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Mon, 22 Aug 2022 16:54:59 +0200
Subject: [PATCH 17/20] Add `metaFields` -> `allowedMetaFields` breaking change

---
 website/src/docs/migration-guides.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 5389791c7e..0956200f34 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -157,6 +157,12 @@ It’s internal usage only.
 
 To migrate: use exposed options only.
 
+#### `@uppy/tus/`, `@uppy/aws-s3`, `@uppy/xhr-upload`
+
+Rename `metaFields` option to `allowedMetaFields`. Counter intuitively, `metaFields` is for _filtering_ which `metaFields` to send along with the request, not for adding extra meta fields to a request. As a lot of people were confused by this, and the name overlaps with the [`metaFields` option from Dashboard](/docs/dashboard/#metaFields), we renamed it.
+
+To migrate: use `allowedMetaFields`.
+
 #### `@uppy/react`
 
 Don’t expose `validProps` on the exported components. They are internal usage only.

From d1adeba1b7a384bffb03128efe50cbc715d56d71 Mon Sep 17 00:00:00 2001
From: Artur Paikin <artur@arturpaikin.com>
Date: Mon, 22 Aug 2022 18:49:06 +0100
Subject: [PATCH 18/20] Update website/src/docs/migration-guides.md

Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
---
 website/src/docs/migration-guides.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 0956200f34..be72fb44ff 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -82,6 +82,8 @@ new Uppy()
   })
 ```
 
+Checkout how we did it on [our own Robodog example](https://github.com/transloadit/uppy/commit/089aaed615c77bafaf905e291b6b4e82aaeb2f6f).
+
 ## Migrate from Uppy 2.x to 3.x
 
 ### Uppy is pure ESM

From 1de0ffedf0318c9c8fefbe17592c39f7728c487b Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Mon, 22 Aug 2022 20:01:14 +0200
Subject: [PATCH 19/20] Add peer dependencies breaking changes

---
 website/src/docs/migration-guides.md | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index be72fb44ff..808a5cb610 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -167,10 +167,24 @@ To migrate: use `allowedMetaFields`.
 
 #### `@uppy/react`
 
-Don’t expose `validProps` on the exported components. They are internal usage only.
+##### Uppy dependencies have become peer dependencies
+
+`@uppy/dashboard`, `@uppy/drag-drop`, `@uppy/file-input`, `@uppy/progress-bar`, and `@uppy/status-bar` are now peer dependencies. This means you don’t install all these packages if you only need one.
+
+To migrate: install only the packages you need. If you use the Dashboard component, you need `@uppy/dashboard`, and so onwards.
+
+##### Don’t expose `validProps` on the exported components.
+
+It’s internal usage only.
 
 To migrate: use exposed options only.
 
+#### `@uppy/vue`
+
+`@uppy/dashboard`, `@uppy/drag-drop`, `@uppy/file-input`, `@uppy/progress-bar`, and `@uppy/status-bar` are now peer dependencies. This means you don’t install all these packages if you only need one.
+
+To migrate: install only the packages you need. If you use the Dashboard component, you need `@uppy/dashboard`, and so onwards.
+
 #### `@uppy/store-redux`
 
 Remove backwards compatible exports (static properties on `ReduxStore`). Exports, such as `reducer`, used to also be accessible on the `ReduxStore` export. This has now been removed due to the transition to ESM.

From 018040a45d29c764f30b3792bfca577d34c69c18 Mon Sep 17 00:00:00 2001
From: Murderlon <merlijn@soverin.net>
Date: Mon, 22 Aug 2022 20:03:30 +0200
Subject: [PATCH 20/20] Improve paragraph about Robodog migration commit

---
 website/src/docs/migration-guides.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/src/docs/migration-guides.md b/website/src/docs/migration-guides.md
index 808a5cb610..b2bfa65634 100644
--- a/website/src/docs/migration-guides.md
+++ b/website/src/docs/migration-guides.md
@@ -23,6 +23,8 @@ This has now led us to deprecating Robodog and embrace Uppy for its strong suits
 
 To mimic the Robodog implementation with all its features, you can use the code snippet below. But chances are Robodog did more than you need so feel free to remove things or go through the [list of plugins](/docs/plugins/) and install and use the ones you need.
 
+You can also checkout how we migrated the Robodog example ourselves in this [commit](https://github.com/transloadit/uppy/commit/089aaed615c77bafaf905e291b6b4e82aaeb2f6f).
+
 ```js
 import Uppy from '@uppy/core'
 import Dashboard from '@uppy/dashboard'
@@ -82,8 +84,6 @@ new Uppy()
   })
 ```
 
-Checkout how we did it on [our own Robodog example](https://github.com/transloadit/uppy/commit/089aaed615c77bafaf905e291b6b4e82aaeb2f6f).
-
 ## Migrate from Uppy 2.x to 3.x
 
 ### Uppy is pure ESM