diff --git a/404.html b/404.html
index d33236dcf..163795cf3 100644
--- a/404.html
+++ b/404.html
@@ -12,7 +12,7 @@
-
+
diff --git a/assets/js/b2f554cd.5913eb2e.js b/assets/js/b2f554cd.5913eb2e.js
deleted file mode 100644
index d7b5d98ce..000000000
--- a/assets/js/b2f554cd.5913eb2e.js
+++ /dev/null
@@ -1 +0,0 @@
-"use strict";(self.webpackChunkuppy_io=self.webpackChunkuppy_io||[]).push([[1477],{30010:e=>{e.exports=JSON.parse('{"blogPosts":[{"id":"2023/07/3.13-3.21","metadata":{"permalink":"/blog/2023/07/3.13-3.21","editUrl":"https://github.com/transloadit/uppy.io/tree/main/blog/2023-12-3.13-3.21.md","source":"@site/blog/2023-12-3.13-3.21.md","title":"\ud83c\udf84 Uppy 3.13 to 3.21: Typescript Saga: the beginning, Image Editor improvements, Dashboard auto-install","description":"It\u2019s this time of the year again! Make yourself cozy","date":"2023-12-23T00:00:00.000Z","formattedDate":"December 23, 2023","tags":[],"readingTime":4.62,"hasTruncateMarker":true,"authors":[{"email":"antoine@transloadit.com","name":"Antoine du Hamel","id":"aduh95","tagline":"Developer","imageURL":"https://github.com/aduh95.png","key":"aduh95"},{"email":"merlijn@transloadit.com","name":"Merlijn Vos","id":"merlijn","tagline":"Developer","imageURL":"https://github.com/murderlon.png","key":"murderlon"},{"email":"artur@transloadit.com","name":"Artur Paikin","id":"artur","tagline":"Developer","imageURL":"https://github.com/arturi.png","key":"arturi"},{"email":"mikael@transloadit.com","name":"Mikael Finstad","id":"mikael","tagline":"Developer","imageURL":"https://github.com/mifi.png","key":"mifi"}],"frontMatter":{"title":"\ud83c\udf84 Uppy 3.13 to 3.21: Typescript Saga: the beginning, Image Editor improvements, Dashboard auto-install","date":"2023-12-23T00:00:00.000Z","authors":["aduh95","murderlon","arturi","mifi"],"image":"https://uppy.io/img/blog/3.13-3.21/dog-coding-laptop-mars-christmas-tree.jpg","slug":"2023/07/3.13-3.21","published":true,"toc_max_heading_level":2},"unlisted":false,"nextItem":{"title":"Scaling Images on Rotation","permalink":"/blog/2023-10-25-image-editor"}},"content":"\\n\\nIt\u2019s this time of the year again! Make yourself cozy\\n[by the fire](https://www.youtube.com/watch?v=ouqtX6WWL1U), and let us help you\\nunwrap the gifts Uppy has prepared for you.\\n\\nWe proud of all the improvements and amazing new features and bug fixes we were\\nable to introduce this year. The highlights being: conditional S3 multipart and\\nsigning S3 uploads on the client, speedy handling of 10-50k file uploads,\\nrefresh tokens (useful when the token expires mid-upload for a large amount of\\nfiles / slow connections), server-sent events and new `assemblyOptions` for the\\nTransloadit plugin, Dashboard Single File mode (`singleFileFullScreen`),\\nimproved ETA in the Status Bar, a bunch of new languages, including Hindi,\\nMexican Spanish and Catalan.\\n\\nThis one, however, is a recent Uppy updates post, covering releases from\\n[`3.13.0` to `3.21.0`](https://github.com/transloadit/uppy/compare/uppy%403.13.0...uppy%403.21.0):\\nannouncing the switch to Typescript, Dashboard can now auto-install plugins,\\nsupport for Catalan language, a heap of bug fixes for Tus, Companion, AWS S3,\\nand more.\\n\\n\x3c!--truncate--\x3e\\n\\n## Typescript\\n\\nWe are excited to announce that we are working hard to refactor Uppy Core and\\nall plugins source files to TypeScript. We have a build setup in place that\\ntemporarily supports both `.ts` and `.js` files in our monorepo. And a helper\\nutility that takes a package name and does the initial renaming and Typescript\\nconfig. Then we go through the list of plugins one by one. We begun with\\n`@uppy/utils` and `@uppy/core`, since most other packages depend on those. Now\\nwe are moving to the rest, one by one.\\n\\nThis work so far is only affecting Uppy internals. In published packages we are\\nusing the manually crafted `d.ts` files, as before. We are planning to flip the\\nswitch and introduce some breaking changes in the next Uppy major, due to be\\nreleased in the first quater of 2024.\\n\\n## Core\\n\\n- Allow duplicate files with `onBeforeFileAdded`.\\n- Fixed`onBeforeFileAdded` with Golden Retriever.\\n- Simplify types with class generic and type more events.\\n\\n## Image Editor\\n\\nWe have a whole separate blog post about the recent rotation improvements in the\\nImage Editor, so please read that, if you are interested. Other changes include:\\n\\n- Fixed labels on all buttons, centered the rotation slider label.\\n- Limited cropbox movements.\\n- Fixed to respect `cropperOptions.initialAspectRatio`.\\n- Change the checkered background color, make it semi-transparent.\\n- Fixed granular rotation: `[-45, 45]` instead of `[-45, 44]`.\\n- Removed 1px black lines.\\n- Made `file-editor:cancel` event fire when the Image Editor\u2019s \u201ccancel\u201d button\\n is pressed.\\n\\n\\n\\n\\n\\n## Dashboard\\n\\nDashboard can now automatically discover and install compatible plugins without\\n`target` option. This lets you use a much more condense syntax:\\n\\n```js\\nconst uppy = new Uppy()\\n\\t.use(ImageEditor)\\n\\t.use(Dashboard)\\n\\t.use(Webcam)\\n\\t.use(GoogleDrive);\\n```\\n\\n:::tip \\n\\nThe old way via `.use(ImageEditor, { target: Dashboard })` and\\n`.use(Dashboard, { plugins: [\'Webcam\', \'GoogleDrive\'] })` still works, but we\\nencourage you to use the new syntax.\\n\\n:::\\n\\nBug fixes:\\n\\n- Remove `.uppy-Dashboard-isFixed` CSS class when `uppy.close()` is invoked.\\n- When `showAddFilesPanel: true`, `aria-hidden` should be the opposite.\\n- Don\u2019t cancel all files and Assemblies when clicking \u201cdone\u201d.\\n- Update Dashboard\u2019s blue color to meet WCAG contrast requirements.\\n\\n## AWS S3\\n\\n- Fixed `TypeError`, fixed `uploadURL` when using `PUT`.\\n- Pass `signal` as separate arg for backward compat; pass the `uploadURL` back\\n to the caller.\\n- Refresh file before calling user-defined functions.\\n- Made sure we retry signature request.\\n- Use uppercase HTTP method names.\\n- Call `#setCompanionHeaders` in `setOptions`.\\n\\n## Companion\\n\\nOne of the most notable changes in Companion is on the client side, we\u2019ve made\\nauthentication optional, allowing for more provider types, with publicly\\naccessable links, for example.\\n\\nIn Companion Client we were able to drop the now unnecessary preflight requests,\\nimproving upload speeds and latency yet again.\\n\\nOther notable changes and fixes:\\n\\n- Allow dynamic S3 bucket.\\n- Companion+client stability fixes, error handling and retries.\\n- Catch \u201cinvalid initialization vector\u201d instead of crashing.\\n- Added Onedrive refresh tokens.\\n- Fixed `authProvider` property inconsistency.\\n- Fixed accelerated endpoints for presigned POST.\\n- Fixed double tus uploads.\\n- Fixed onedrive pagination.\\n- Fixed Redis key default TTL.\\n- Fixed Uploader.js metadata normalisation.\\n- Make CSRF protection helpers available to providers.\\n- Refactor `getProtectedHttpAgent` to make TS happy.\\n- Unify redis initialization.\\n- Use deferred length for tus streams.\\n- Fixed a refresh token race condition.\\n- Fixed edge case for pagination on root.\\n- Fixed instagram/facebook auth error regression; uploadRemoteFile undefined;\\n ProviderView error on empty plugin.icon.\\n- Added getBucket metadata argument.\\n- Added missing credentialsURL for box.\\n- Added test endpoint for dynamic oauth creds.\\n- Added Companion OAuth Key type.\\n- Aliased \u201cremoveListener\u201d as \u201coff\u201d in Redis emitter.\\n- Use user-defined `onSuccess`, `onError`, and `onProgress` callbacks in\\n `@uppy/tus`.\\n- Invoke headers function for remote uploads.\\n- Send certain Onedrive errors to the user.\\n- Upgraded Node.js docker version.\\n\\n## Frameworks Integraions\\n\\n- Angular: upgraded to Angular 16.x.\\n- Svelte: Fixed TS build command.\\n- Vue: added export for FileInput.\\n\\n## Locales\\n\\n- Added Catalan locale `ca_ES`.\\n- Added missing translations to `de_DE`.\\n- Update Farsi.\\n\\n## Transloadit\\n\\n- Emit assembly progress events.\\n- Removed Socket.io \u2014 it\u2019s server-sent events with fallback to polling now.\\n\\n## Misc\\n\\n- Added Prettier, migrated to Vitest for Uppy core and Uppy plugins.\\n- Update `file.meta.name` after compression, becase format/extension might have\\n changed.\\n- use latest Node.js version for tests.\\n- Migrate to AWS-SDK V3 syntax.\\n- Move remote file upload logic into companion-client.\\n\\nHappy holidays and see you in 2024!"},{"id":"2023-10-25-image-editor","metadata":{"permalink":"/blog/2023-10-25-image-editor","editUrl":"https://github.com/transloadit/uppy.io/tree/main/blog/2023-10-25-image-editor.md","source":"@site/blog/2023-10-25-image-editor.md","title":"Scaling Images on Rotation","description":"We recently released an \u201cimage scaling on rotation\u201d feature for Uppy\u2019s","date":"2023-12-08T00:00:00.000Z","formattedDate":"December 8, 2023","tags":[],"readingTime":5.805,"hasTruncateMarker":true,"authors":[{"email":"lakesare@gmail.com","name":"Evgenia Karunus","id":"evgenia","tagline":"Developer","imageURL":"https://github.com/lakesare.png","key":"evgenia"},{"email":"tim@transloadit.com","name":"Tim Koschuetzki","id":"tim","tagline":"Transloadit co-founder","imageURL":"https://github.com/tim-kos.png","key":"tim"}],"frontMatter":{"title":"Scaling Images on Rotation","date":"2023-12-08T00:00:00.000Z","authors":["evgenia","tim"],"image":"/img/blog/3.4-3.13/single-file-mode.jpg","slug":"2023-10-25-image-editor","published":true,"toc_max_heading_level":3},"unlisted":false,"prevItem":{"title":"\ud83c\udf84 Uppy 3.13 to 3.21: Typescript Saga: the beginning, Image Editor improvements, Dashboard auto-install","permalink":"/blog/2023/07/3.13-3.21"},"nextItem":{"title":"Uppy 3.3 to 3.13: conditional S3 multipart, signing on the client, speedy handling of 10k files and much much more","permalink":"/blog/2023/07/3.3-3.13"}},"content":"\x3c!--retext-simplify disable prior-to all-of employ very represents appropriate--\x3e\\n\\nWe recently released an \u201cimage scaling on rotation\u201d feature for Uppy\u2019s\\n[Image Editor](https://uppy.io/docs/image-editor/), an often-requested feature\\nthat we\u2019re super proud to be able to announce.\\n\\nIn this blog post, we\u2019ll be taking a peek behind the curtain, as we take a\\ndetailed look into the development of this feature, and our thought-process\\napproaching it.\\n\\nBefore we start though, take a look below at a comparison between how Uppy\u2019s\\nImage Editor used to handle image rotations, and how it handles them now.\\n\\n
\\n \\n
\\n
\\n Rotation\\n
\\n
\\n\\n
\\n
Without scaling
\\n
With scaling
\\n
\\n \\n\\n \\n
\\n
\\n \\n
\\n\\n
\\n \\n
\\n
\\n \\n
\\n\\nWithout further ado, let\u2019s dive into some of the finer technical details, so you\\ncan follow along and implement this feature into your own image editor.\\n\\n\x3c!--truncate--\x3e\\n\\nThe above UI is present in many image editors - for example, the default image\\neditors on iOS and Android both employ it. Often users expect this behaviour\\ntoo, leading to some confusion when their images are left with ugly corners\\nafter a rotation.\\n\\nWe implemented this in Uppy\u2019s Image Editor last week, and the solution turned\\nout to be non-trivial. Since this is a pretty ubiquitous task to solve for all\\nimage editors, we decided to release our solution to the world and write out a\\npost about it, instead of keeping it hidden away as part of internal notes.\\n\\n## 3 Steps\\n\\nThere are **3 steps** to our scaling implementation:\\n\\n1. Ask your designer what scaling on rotation should look like\\n1. Find the `.scale()` function\\n1. Calculating the geometry\\n\\n### 1. Trust your designer\\n\\nWhen I first approached this task, my gut-instinct was to go for the \u201crotated\\nrectangle inscribed within another rectangle\u201d solution so that the largest-area\\ninscription possible is achieved. This route turned out to be an unpleasant user\\nexperience, so take this as an important lesson in trusting your designer, and\\nconsulting them first on what the user might want.\\n\\nAlternatively, you can choose to trust our designer\u2019s advice by:\\n\\n- always rotating the image around the center of the image (intersection of the\\n diagonals)\\n- just enlarging the image to remove any empty corners\\n\\n### 2. Find the `.scale()` function\\n\\nTo enlarge the image in a way that covers empty corners, we first need a scaling\\nfunction. Uppy uses [cropperjs v1.x](https://github.com/fengyuanchen/cropperjs)\\nas an image editing library, which exposes the `cropper.scale(scalingFactor)`\\nfunction. Most image editing libraries are likely to have a similar function,\\nbut of course feel free to code one yourself if you feel up to the challenge.\\n\\nImportantly, the scaling function should\\n[uniformly enlarge]()\\nthe image _around its center_, where the `scalingFactor` is determined by\\n`desiredHeight/oldHeight`.\\n\\n### 3. Calculate the geometry\\n\\nNow, we want to draw our before-rotation & after-rotation shapes on the same\\npicture, and apply some trigonometry. If you need to brush up on the mathematics\\nbehind this, we recommend watching the following Khan Academy lessons on\\n[how angles work](https://www.khanacademy.org/test-prep/praxis-math/praxis-math-lessons/gtp--praxis-math--lessons--geometry/a/gtp--praxis-math--article--angles--lesson)\\nand\\n[how sines and cosines work](https://www.khanacademy.org/math/geometry/hs-geo-trig/hs-geo-trig-ratios-intro/a/finding-trig-ratios-in-right-triangles),\\nas these cover everything you\u2019ll need to follow along.\\n\\nIn the images below, we see what happens on rotation by default. To remove the\\nempty corners, the user would have to drag around the edges of the cropbox. What\\nwe can do instead is scale the image (in the directions shown by the green arrows) so that these\\ncorners disappear.\\n\\n
\\n \\n
What happens on rotation
\\n \\n\\n \\n
\\n
\\n \\n
\\n\\n
\\n \\n
\\n
\\n \\n
\\n\\nSo, to cover up these checkered corners, we will need to scale the image. If we\\ncover up the larger corner, the smaller corner will get covered up\\nautomatically, so our code takes the form of\\n`scale(Math.max(scalingFactor1, scalingFactor2))`. These two scaling factors are\\ncalculated very similarly, so we\u2019ll only focus on calculating only one of them\\nin this tutorial (although the full solution is given in the conclusion).\\n\\nIn the images below, the green\\nrectangle represents the desired dimensions of our image after it\u2019s\\nscaled. Our scaling function (and hopefully yours) is defined in such a way that\\nif we have the image of height `h`, and we want to scale it up to height `H`, we\\nneed to execute `.scale(H/h)`. Since we already know `h`, as it\u2019s the height of\\nour image, we only need to find `H` to complete our scaling function.\\n\\n
\\n \\n
We want to find H
\\n \\n\\n \\n
\\n
\\n \\n
\\n\\n
\\n \\n
\\n
\\n \\n
\\n\\nFor the rest of the tutorial, the following steps are then automatic - as we\\nknow all the angles in the image, we know the image\u2019s width and height, and we\\nknow to find `H`.\\n\\n
The easiest way to go about it, is to first annotate the image with all the\\nrelevant angles. We\u2019ll be using blue for the rotation angle\\n \u03b1, and pink \\nfor 90 - \u03b1:
\\n\\n
\\n \\n
Color all angles
\\n \\n\\n \\n
\\n
\\n \\n
\\n
\\n \\n
\\n\\nWe can then find `H`, by adding the two outer sides of these triangles.\\n\\n
\\n \\n
Add two triangle sides: H = sin(\u03b1 - 90) * h + sin(\u03b1) * w
\\n \\n\\n \\n
\\n
\\n \\n
\\n\\n
\\n \\n
\\n
\\n \\n
\\n\\nSo, now we have our desired `H`! We know one of our scaling factors is `H/h`.\\nNow, we just need to find our other scaling factor, which is `W/w`. This follows\\na similar process, and you can find the calculations as part of the full\\nsolution below.\\n\\n```javascript\\nscalingFactor\\n= max(scalingFactor1, scalingFactor2)\\n= max(H/h, W/w)\\n= max(\\n (sin(\u03b1 - 90) * h + sin(\u03b1) * w) / h,\\n (sin(\u03b1) * h + sin(\u03b1 - 90) * w) / w\\n)\\n```\\n\\n## Conclusion\\n\\nIn Uppy, our code ended up looking like this:\\n\\n```javascript\\nfunction getScalingFactor(w, h, rotationAngle) {\\n\\tconst \u03b1 = Math.abs(toRadians(rotationAngle));\\n\\n\\tconst scalingFactor = Math.max(\\n\\t\\t(Math.sin(\u03b1) * w + Math.cos(\u03b1) * h) / h,\\n\\t\\t(Math.sin(\u03b1) * h + Math.cos(\u03b1) * w) / w,\\n\\t);\\n\\n\\treturn scalingFactor;\\n}\\nconst image = cropper.getImageData();\\nconst scaleFactor = getScalingFactor(image.width, image.height, rotationAngle);\\ncropper.scale(scaleFactor);\\n```\\n\\nYou can see the full version\\n[on GitHub](https://github.com/transloadit/uppy/blob/12e08ada02b9080bd5e1d19526bdf8a2010e62a1/packages/%40uppy/image-editor/src/utils/getScaleFactorThatRemovesDarkCorners.js).\\n\\n\\n Bonus content: our founder\u2019s (Tim Koschuetzki) initial scribbled notes with the solution\\n \\n"},{"id":"2023/07/3.3-3.13","metadata":{"permalink":"/blog/2023/07/3.3-3.13","editUrl":"https://github.com/transloadit/uppy.io/tree/main/blog/2023-07-3.4-3.13.md","source":"@site/blog/2023-07-3.4-3.13.md","title":"Uppy 3.3 to 3.13: conditional S3 multipart, signing on the client, speedy handling of 10k files and much much more","description":"This is a big Uppy update post, covering releases from","date":"2023-07-26T00:00:00.000Z","formattedDate":"July 26, 2023","tags":[],"readingTime":8.82,"hasTruncateMarker":true,"authors":[{"email":"merlijn@transloadit.com","name":"Merlijn Vos","id":"merlijn","tagline":"Developer","imageURL":"https://github.com/murderlon.png","key":"murderlon"},{"email":"artur@transloadit.com","name":"Artur Paikin","id":"artur","tagline":"Developer","imageURL":"https://github.com/arturi.png","key":"arturi"},{"email":"antoine@transloadit.com","name":"Antoine du Hamel","id":"aduh95","tagline":"Developer","imageURL":"https://github.com/aduh95.png","key":"aduh95"},{"email":"mikael@transloadit.com","name":"Mikael Finstad","id":"mikael","tagline":"Developer","imageURL":"https://github.com/mifi.png","key":"mifi"}],"frontMatter":{"title":"Uppy 3.3 to 3.13: conditional S3 multipart, signing on the client, speedy handling of 10k files and much much more","date":"2023-07-26T00:00:00.000Z","authors":["murderlon","arturi","aduh95","mifi"],"image":"/img/blog/3.4-3.13/single-file-mode.jpg","slug":"2023/07/3.3-3.13","published":true,"toc_max_heading_level":2},"unlisted":false,"prevItem":{"title":"Scaling Images on Rotation","permalink":"/blog/2023-10-25-image-editor"},"nextItem":{"title":"New Uppy.io and docs","permalink":"/blog/2023-05-new-website"}},"content":"\\n\\nThis is a big Uppy update post, covering releases from\\n[`3.3.0` to `3.13.0`](https://github.com/transloadit/uppy/compare/uppy%403.4.0...uppy%403.13.0)!\\n\\nIn this issue: the long-awaited unified S3 plugin which can switch between\\nregular and multipart uploads, improved performance when adding and validating\\n10k+ files, and stability improvements and bug fixes. The Transloadit plugin is\\nnow also easier to configure and leaner in bundle size, since we removed\\n`socket.io-client` in favor of\\n[Server-Sent Events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events).\\n\\nPlease make a cup of something tasty \u2615\ufe0f (in a non-spillable container), as this\\nwill be quite a ride.\\n\\n\x3c!--truncate--\x3e\\n\\n## AWS S3\\n\\n### Merging of the plugins\\n\\nAfter years of separating regular non-multipart uploads and multipart uploads,\\nwe are finally merging the two sibling plugins: `@uppy/aws-s3` and\\n`@uppy/aws-s3-multpart`. Here\u2019s the brief version of what you need to know, with\\ndetails to follow in the next section:\\n\\n- `@uppy/aws-s3-multipart` is deprecated. You should use `@uppy/aws-s3` and set\\n the `shouldUseMultipart: true` option to get the same \u201cmultipart always\\n enabled\u201d behavior. We plan to keep `@uppy/aws-s3-multipart` around as an alias\\n for the next major cycle and add a warning at the install when Uppy 4.0.0 will\\n be released.\\n- `@uppy/aws-s3` now hosts two plugins:\\n - the legacy one, untouched, to guarantee backward compatibility. We plan to\\n get rid of it in the next major, we recommend moving away from it and report\\n if you see something missing in the new plugin.\\n - the new merged plugin, available if you pass\\n [`shouldUseMultipart`](https://uppy.io/docs/aws-s3-multipart/#shouldusemultipartfile)\\n option.\\n\\nOur plan for this merge is to maintain the backward compatibility until the next\\nmajor, while also providing forward compatibility so you can try our new plugin\\nand give us some feedback before we remove the old code for good.\\n\\n### Conditional Multipart Explained\\n\\nMultipart and \u201cregular\u201d uploads have different use cases. The advantages of\\nmultipart uploads are:\\n\\n- **Improved throughput** \u2013 You can upload parts in parallel to improve\\n throughput.\\n- **Quick recovery from any network issues** \u2013 Smaller part size minimizes the\\n impact of restarting a failed upload due to a network error.\\n- **Pause and resume object uploads** \u2013 You can upload object parts over time.\\n After you initiate a multipart upload, there is no expiry; you must explicitly\\n complete or stop the multipart upload.\\n- **Begin an upload before you know the final object size** \u2013 You can upload an\\n object as you are creating it.\\n\\nHowever, the downside is _request overhead_, as it needs to do creation,\\nsigning, and completion requests besides the upload requests. For example, if\\nyou are uploading files that are only a couple kilobytes with a 100ms roundtrip\\nlatency, you are spending 400ms on overhead and only a few milliseconds on\\nuploading. This really adds up if you upload a lot of small files.\\n\\nSo now you can use just one plugin, the `@uppy/aws-s3`, and enable multipart\\nconditionally, even per-file:\\n\\n```js\\nuppy.use(AwsS3, {\\n\\tshouldUseMultipart(file) {\\n\\t\\t// Use multipart only for files larger than 100MiB.\\n\\t\\treturn file.size > 100 * 2 ** 20;\\n\\t},\\n});\\n```\\n\\nor\\n\\n```js\\nuppy.use(AwsS3, {\\n\\tshouldUseMultipart: true,\\n});\\n```\\n\\nPlease see the new\\n[`shouldUseMultipart: boolean | function`](https://uppy.io/docs/aws-s3-multipart/#shouldusemultipartfile)\\noption for details.\\n\\n### Signing on the client\\n\\nBy default, when you upload to S3 with Uppy, every file, or every chunk in case\\nof Multipart, needs to be signed on the server. For many small files or files\\nwith many chunks this means a few additional requests per file/chunk of the\\nupload.\\n\\nTo address this issue and speed up the uploads by roughly 20%, we are\\nintroducing a new option: `getTemporarySecurityCredentials: boolean | function`.\\nWhen `true`, both S3 and S3 Multipart uploads will be signed on the client using\\nthe\\n[AWS Security Federation Token](https://docs.aws.amazon.com/STS/latest/APIReference/API_GetFederationToken.html),\\ncreated once per user (until it expires) on your backend rather than a unique\\nsigned URL for every single chunk.\\n\\n:::caution\\n\\nYou should opt-in into this only if you are comfortable giving end users direct\\naccess to signing files for your bucket.\\n\\n:::\\n\\n### Stability and bug fixes\\n\\n- We\u2019ve improved the internal handling of `RateLimitedQueue` to make\\n [retries more robust](https://github.com/transloadit/uppy/pull/4424) and\\n increased\\n [priority of `abort` and `complete`](https://github.com/transloadit/uppy/pull/4542)\\n requests.\\n- While we were at it, we\u2019ve also fixed\\n [resuming in single-chunk uploads](https://github.com/transloadit/uppy/pull/4528),\\n and improved\\n [chunk size calculation](https://github.com/transloadit/uppy/pull/4508).\\n- [Golden Retriever integration with S3 Multipart](https://github.com/transloadit/uppy/pull/4526)\\n was fixed.\\n\\nAdditionally, we\u2019ve disabled pause-resume buttons in the UI for remote S3\\nMultipart uploads \u2014\xa0they are not supported on Companion, so the UI now reflects\\nthat.\\n\\n## Core\\n\\nPerformance of adding and uploading big batches of files has (yet again) been\\ngreatly improved with refactors in both Uppy Core and Provider Views (that\u2019s\\nwhat we internally call all remote UIs: Instagram, Unsplash, Dropbox).\\n\\nWe\u2019ve been able to achieve this by\\n[refactoring out totals validation for Restrictions (maxTotalFileSize, maxNumberOfFiles)](https://github.com/transloadit/uppy/pull/4402):\\ninstead of doing it for each file, we perform the check at the end, after all\\nthe files have been added/validated. This was confirmed to work with 10k+ files!\\n\ud83d\ude80\\n\\n\\n\\nWe\u2019ve also fixed an issue with delayed throttled progress events, which could\\nlead to incorrect progress.\\n\\n## Transloadit\\n\\n### assemblyOptions\\n\\nWe\u2019ve introduced a new option called\\n[`assemblyOptions: object | function`](https://uppy.io/docs/transloadit/#assemblyoptions),\\nwhich replaces the `getAssemblyOptions`, `params` and `fields` (those are now\\ndeprecated and will be removed in the next major).\\n\\nHere\u2019s how you can use the new option as an object:\\n\\n```js\\nuppy.use(Transloadit, {\\n\\tassemblyOptions: {\\n\\t\\tparams: {\\n\\t\\t\\tauth: { key: \'key-from-transloadit\' },\\n\\t\\t\\ttemplate_id: \'id-from-transloadit\',\\n\\t\\t\\tsteps: {\\n\\t\\t\\t\\t// Overruling Template at runtime\\n\\t\\t\\t},\\n\\t\\t},\\n\\t\\tsignature: \'generated-signature\',\\n\\t\\tfields: {\\n\\t\\t\\t// Dynamic or static fields to send along\\n\\t\\t},\\n\\t},\\n});\\n```\\n\\nAnd here\u2019s an example with a function, to be able to set meta fields per-file,\\nfor instance:\\n\\n```js\\nuppy.use(Transloadit, {\\n\\tassemblyOptions(file) {\\n\\t\\treturn {\\n\\t\\t\\tparams: {\\n\\t\\t\\t\\tauth: { key: \'TRANSLOADIT_AUTH_KEY_HERE\' },\\n\\t\\t\\t\\ttemplate_id: \'xyz\',\\n\\t\\t\\t},\\n\\t\\t\\tfields: {\\n\\t\\t\\t\\tcaption: file.meta.caption,\\n\\t\\t\\t},\\n\\t\\t};\\n\\t},\\n});\\n```\\n\\n### Server-sent events\\n\\nHistorically Transloadit supported progress updates via Socket.io. It is a\\nrobust and stable package, but came with a \u201cprice-tag\u201d in the form of bundle\\nsize:\\n[38.3 kB Minified](https://bundlephobia.com/package/socket.io-client@4.7.1). So\\nit\u2019s been on our minds for a while to replace it with something more\\nlightweight, without breaking backwards-compatibility for the older clients (so\\nsimply removing Socket.io on the server in favor of plain WebSockets is not\\ndesireable).\\n\\nThe answer \u2014\\n[Server-sent events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events).\\nIt\u2019s a simple low-overhead one-way connection from Transloadit servers to\\n`@uppy/transloadit`. As was the case with Socket.io, we fall back to HTTP\\npolling every 2 seconds if SSE connection fails for some reason.\\n\\nSocket.io is still around in `@uppy/transloadit`, but will be removed soon, once\\nSSE proves itself in production.\\n\\n### Bug fixes\\n\\n- Reset `tus` key in the file on error, so retried files are re-uploaded.\\n- Clean up event listener to prevent cancelled assemblies.\\n- Make sure `fields` is not nullish when there are no files in Assembly.\\n\\n## Companion\\n\\n### Refresh tokens\\n\\nWe\u2019ve\\n[implemented refresh tokens](https://github.com/transloadit/uppy/pull/4448) for\\nDropbox and Google Drive to solve issued where tokens would expire in the middle\\nof a long upload and then the upload would fail.\\n\\nHere\u2019s how it\u2019s implemented in Companion:\\n\\n- We changed the logic when receiving a 401 from Companion, Uppy will now call a\\n new `/:provider/refresh-token` endpoint which will give uppy a new access\\n token.\\n- `refresh_token` is now stored inside uppy auth token along with `access_token`\\n (encrypted JWT) for providers that give a refresh token (before only\\n `access_token` was stored, now we store both as a `JSON.stringify`\u2019d\\n document).\\n\\n### Bug fixes and improvements\\n\\n- Fixed a bug with non-ASCII metadata crashed Companion. The AWS SDK doesn\u2019t\\n encode metadata by itself, so now we do it in Companion.\\n- Switched from aws-sdk v2 to @aws-sdk/\\\\* v3\\n- Upgraded Grant dependency\\n- We now send expire info for non-multipart uploads and added connection\\n keep-alive to Dropbox to improve connection stability\\n- Merged Provider and SearchProvider internal remote source classes.\\n- Increased max limits for remote file list operations and fixed part listing in\\n S3\\n\\n## Url\\n\\nWe\u2019ve upgraded the Url plugin to use `filename` from `Content-Disposition`\\nheader of the file you are importing, instead of relying on the url (but kept\\nthe latter as a fallback) (#4489). So now your files have proper names instead\\nof `noname`.\\n\\n\\n\\n## Dashboard and Status Bar\\n\\nSingle File Mode has been improved to adapt to height of less than 400px \u2014 the\\nUI turns back to grid in this case. We are also not using `fit: cover` anymore\\nto avoid cropping important parts of the image:\\n\\n\\n\\nWe\u2019ve also added an option to disable the Single File mode, as it can be\\nunwanted in certain use cases:\\n[`singleFileFullScreen`](https://uppy.io/docs/dashboard/#singlefilefullscreen).\\n\\nIf you wrapped Uppy Dashboard in a `
![\\"Screenshot](\\"/img/blog/3.13-3.21/dog-coding-laptop-mars-christmas-tree.jpg\\")
\\n\\nIt\u2019s this time of the year again! Make yourself cozy\\n[by the fire](https://www.youtube.com/watch?v=ouqtX6WWL1U), and let us help you\\nunwrap the gifts Uppy has prepared for you.\\n\\nWe proud of all the improvements and amazing new features and bug fixes we were\\nable to introduce this year. The highlights being: conditional S3 multipart and\\nsigning S3 uploads on the client, speedy handling of 10-50k file uploads,\\nrefresh tokens (useful when the token expires mid-upload for a large amount of\\nfiles / slow connections), server-sent events and new `assemblyOptions` for the\\nTransloadit plugin, Dashboard Single File mode (`singleFileFullScreen`),\\nimproved ETA in the Status Bar, a bunch of new languages, including Hindi,\\nMexican Spanish and Catalan.\\n\\nThis one, however, is a recent Uppy updates post, covering releases from\\n[`3.13.0` to `3.21.0`](https://github.com/transloadit/uppy/compare/uppy%403.13.0...uppy%403.21.0):\\nannouncing the switch to Typescript, Dashboard can now auto-install plugins,\\nsupport for Catalan language, a heap of bug fixes for Tus, Companion, AWS S3,\\nand more.\\n\\n\x3c!--truncate--\x3e\\n\\n## Typescript\\n\\nWe are excited to announce that we are working hard to refactor Uppy Core and\\nall plugins source files to TypeScript. We have a build setup in place that\\ntemporarily supports both `.ts` and `.js` files in our monorepo. And a helper\\nutility that takes a package name and does the initial renaming and Typescript\\nconfig. Then we go through the list of plugins one by one. We begun with\\n`@uppy/utils` and `@uppy/core`, since most other packages depend on those. Now\\nwe are moving to the rest, one by one.\\n\\nThis work so far is only affecting Uppy internals. In published packages we are\\nusing the manually crafted `d.ts` files, as before. We are planning to flip the\\nswitch and introduce some breaking changes in the next Uppy major, due to be\\nreleased in the first quater of 2024.\\n\\n## Core\\n\\n- Allow duplicate files with `onBeforeFileAdded`.\\n- Fixed`onBeforeFileAdded` with Golden Retriever.\\n- Simplify types with class generic and type more events.\\n\\n## Image Editor\\n\\nWe have a whole separate blog post about the recent rotation improvements in the\\nImage Editor, so please read that, if you are interested. Other changes include:\\n\\n- Fixed labels on all buttons, centered the rotation slider label.\\n- Limited cropbox movements.\\n- Fixed to respect `cropperOptions.initialAspectRatio`.\\n- Change the checkered background color, make it semi-transparent.\\n- Fixed granular rotation: `[-45, 45]` instead of `[-45, 44]`.\\n- Removed 1px black lines.\\n- Made `file-editor:cancel` event fire when the Image Editor\u2019s \u201ccancel\u201d button\\n is pressed.\\n\\n\\n\\n![\\"Editor](\\"/img/blog/3.13-3.21/editor.jpg\\")
\\n\\n## Dashboard\\n\\nDashboard can now automatically discover and install compatible plugins without\\n`target` option. This lets you use a much more condense syntax:\\n\\n```js\\nconst uppy = new Uppy()\\n\\t.use(ImageEditor)\\n\\t.use(Dashboard)\\n\\t.use(Webcam)\\n\\t.use(GoogleDrive);\\n```\\n\\n:::tip \\n\\nThe old way via `.use(ImageEditor, { target: Dashboard })` and\\n`.use(Dashboard, { plugins: [\'Webcam\', \'GoogleDrive\'] })` still works, but we\\nencourage you to use the new syntax.\\n\\n:::\\n\\nBug fixes:\\n\\n- Remove `.uppy-Dashboard-isFixed` CSS class when `uppy.close()` is invoked.\\n- When `showAddFilesPanel: true`, `aria-hidden` should be the opposite.\\n- Don\u2019t cancel all files and Assemblies when clicking \u201cdone\u201d.\\n- Update Dashboard\u2019s blue color to meet WCAG contrast requirements.\\n\\n## AWS S3\\n\\n- Fixed `TypeError`, fixed `uploadURL` when using `PUT`.\\n- Pass `signal` as separate arg for backward compat; pass the `uploadURL` back\\n to the caller.\\n- Refresh file before calling user-defined functions.\\n- Made sure we retry signature request.\\n- Use uppercase HTTP method names.\\n- Call `#setCompanionHeaders` in `setOptions`.\\n\\n## Companion\\n\\nOne of the most notable changes in Companion is on the client side, we\u2019ve made\\nauthentication optional, allowing for more provider types, with publicly\\naccessable links, for example.\\n\\nIn Companion Client we were able to drop the now unnecessary preflight requests,\\nimproving upload speeds and latency yet again.\\n\\nOther notable changes and fixes:\\n\\n- Allow dynamic S3 bucket.\\n- Companion+client stability fixes, error handling and retries.\\n- Catch \u201cinvalid initialization vector\u201d instead of crashing.\\n- Added Onedrive refresh tokens.\\n- Fixed `authProvider` property inconsistency.\\n- Fixed accelerated endpoints for presigned POST.\\n- Fixed double tus uploads.\\n- Fixed onedrive pagination.\\n- Fixed Redis key default TTL.\\n- Fixed Uploader.js metadata normalisation.\\n- Make CSRF protection helpers available to providers.\\n- Refactor `getProtectedHttpAgent` to make TS happy.\\n- Unify redis initialization.\\n- Use deferred length for tus streams.\\n- Fixed a refresh token race condition.\\n- Fixed edge case for pagination on root.\\n- Fixed instagram/facebook auth error regression; uploadRemoteFile undefined;\\n ProviderView error on empty plugin.icon.\\n- Added getBucket metadata argument.\\n- Added missing credentialsURL for box.\\n- Added test endpoint for dynamic oauth creds.\\n- Added Companion OAuth Key type.\\n- Aliased \u201cremoveListener\u201d as \u201coff\u201d in Redis emitter.\\n- Use user-defined `onSuccess`, `onError`, and `onProgress` callbacks in\\n `@uppy/tus`.\\n- Invoke headers function for remote uploads.\\n- Send certain Onedrive errors to the user.\\n- Upgraded Node.js docker version.\\n\\n## Frameworks Integraions\\n\\n- Angular: upgraded to Angular 16.x.\\n- Svelte: Fixed TS build command.\\n- Vue: added export for FileInput.\\n\\n## Locales\\n\\n- Added Catalan locale `ca_ES`.\\n- Added missing translations to `de_DE`.\\n- Update Farsi.\\n\\n## Transloadit\\n\\n- Emit assembly progress events.\\n- Removed Socket.io \u2014 it\u2019s server-sent events with fallback to polling now.\\n\\n## Misc\\n\\n- Added Prettier, migrated to Vitest for Uppy core and Uppy plugins.\\n- Update `file.meta.name` after compression, becase format/extension might have\\n changed.\\n- use latest Node.js version for tests.\\n- Migrate to AWS-SDK V3 syntax.\\n- Move remote file upload logic into companion-client.\\n\\nHappy holidays and see you in 2024!"},{"id":"2023-10-25-image-editor","metadata":{"permalink":"/blog/2023-10-25-image-editor","editUrl":"https://github.com/transloadit/uppy.io/tree/main/blog/2023-10-25-image-editor.md","source":"@site/blog/2023-10-25-image-editor.md","title":"Scaling Images on Rotation","description":"We recently released an \u201cimage scaling on rotation\u201d feature for Uppy\u2019s","date":"2023-12-08T00:00:00.000Z","formattedDate":"December 8, 2023","tags":[],"readingTime":5.805,"hasTruncateMarker":true,"authors":[{"email":"lakesare@gmail.com","name":"Evgenia Karunus","id":"evgenia","tagline":"Developer","imageURL":"https://github.com/lakesare.png","key":"evgenia"},{"email":"tim@transloadit.com","name":"Tim Koschuetzki","id":"tim","tagline":"Transloadit co-founder","imageURL":"https://github.com/tim-kos.png","key":"tim"}],"frontMatter":{"title":"Scaling Images on Rotation","date":"2023-12-08T00:00:00.000Z","authors":["evgenia","tim"],"image":"/img/blog/3.4-3.13/single-file-mode.jpg","slug":"2023-10-25-image-editor","published":true,"toc_max_heading_level":3},"unlisted":false,"prevItem":{"title":"\ud83c\udf84 Uppy 3.13 to 3.21: Typescript Saga: the beginning, Image Editor improvements, Dashboard auto-install","permalink":"/blog/2023/07/3.13-3.21"},"nextItem":{"title":"Uppy 3.3 to 3.13: conditional S3 multipart, signing on the client, speedy handling of 10k files and much much more","permalink":"/blog/2023/07/3.3-3.13"}},"content":"\x3c!--retext-simplify disable prior-to all-of employ very represents appropriate--\x3e\\n\\nWe recently released an \u201cimage scaling on rotation\u201d feature for Uppy\u2019s\\n[Image Editor](https://uppy.io/docs/image-editor/), an often-requested feature\\nthat we\u2019re super proud to be able to announce.\\n\\nIn this blog post, we\u2019ll be taking a peek behind the curtain, as we take a\\ndetailed look into the development of this feature, and our thought-process\\napproaching it.\\n\\nBefore we start though, take a look below at a comparison between how Uppy\u2019s\\nImage Editor used to handle image rotations, and how it handles them now.\\n\\n![](\\"/img/blog/2023-10-25-image-editor/1a.png\\")
\\n ![](\\"/img/blog/2023-10-25-image-editor/1b.png\\")
\\n ![](\\"/img/blog/2023-10-25-image-editor/2a.png\\")
\\n ![](\\"/img/blog/2023-10-25-image-editor/2b.png\\")
\\n ![](\\"/img/blog/2023-10-25-image-editor/3.png\\")
\\n ![](\\"/img/blog/2023-10-25-image-editor/4a.png\\")
\\n ![](\\"/img/blog/2023-10-25-image-editor/4b.png\\")
\\n ![](\\"/img/blog/2023-10-25-image-editor/tim.jpg\\"/)
\\n![\\"Screenshot](\\"/img/blog/3.4-3.13/single-file-mode.jpg\\")
\\n\\nThis is a big Uppy update post, covering releases from\\n[`3.3.0` to `3.13.0`](https://github.com/transloadit/uppy/compare/uppy%403.4.0...uppy%403.13.0)!\\n\\nIn this issue: the long-awaited unified S3 plugin which can switch between\\nregular and multipart uploads, improved performance when adding and validating\\n10k+ files, and stability improvements and bug fixes. The Transloadit plugin is\\nnow also easier to configure and leaner in bundle size, since we removed\\n`socket.io-client` in favor of\\n[Server-Sent Events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events).\\n\\nPlease make a cup of something tasty \u2615\ufe0f (in a non-spillable container), as this\\nwill be quite a ride.\\n\\n\x3c!--truncate--\x3e\\n\\n## AWS S3\\n\\n### Merging of the plugins\\n\\nAfter years of separating regular non-multipart uploads and multipart uploads,\\nwe are finally merging the two sibling plugins: `@uppy/aws-s3` and\\n`@uppy/aws-s3-multpart`. Here\u2019s the brief version of what you need to know, with\\ndetails to follow in the next section:\\n\\n- `@uppy/aws-s3-multipart` is deprecated. You should use `@uppy/aws-s3` and set\\n the `shouldUseMultipart: true` option to get the same \u201cmultipart always\\n enabled\u201d behavior. We plan to keep `@uppy/aws-s3-multipart` around as an alias\\n for the next major cycle and add a warning at the install when Uppy 4.0.0 will\\n be released.\\n- `@uppy/aws-s3` now hosts two plugins:\\n - the legacy one, untouched, to guarantee backward compatibility. We plan to\\n get rid of it in the next major, we recommend moving away from it and report\\n if you see something missing in the new plugin.\\n - the new merged plugin, available if you pass\\n [`shouldUseMultipart`](https://uppy.io/docs/aws-s3-multipart/#shouldusemultipartfile)\\n option.\\n\\nOur plan for this merge is to maintain the backward compatibility until the next\\nmajor, while also providing forward compatibility so you can try our new plugin\\nand give us some feedback before we remove the old code for good.\\n\\n### Conditional Multipart Explained\\n\\nMultipart and \u201cregular\u201d uploads have different use cases. The advantages of\\nmultipart uploads are:\\n\\n- **Improved throughput** \u2013 You can upload parts in parallel to improve\\n throughput.\\n- **Quick recovery from any network issues** \u2013 Smaller part size minimizes the\\n impact of restarting a failed upload due to a network error.\\n- **Pause and resume object uploads** \u2013 You can upload object parts over time.\\n After you initiate a multipart upload, there is no expiry; you must explicitly\\n complete or stop the multipart upload.\\n- **Begin an upload before you know the final object size** \u2013 You can upload an\\n object as you are creating it.\\n\\nHowever, the downside is _request overhead_, as it needs to do creation,\\nsigning, and completion requests besides the upload requests. For example, if\\nyou are uploading files that are only a couple kilobytes with a 100ms roundtrip\\nlatency, you are spending 400ms on overhead and only a few milliseconds on\\nuploading. This really adds up if you upload a lot of small files.\\n\\nSo now you can use just one plugin, the `@uppy/aws-s3`, and enable multipart\\nconditionally, even per-file:\\n\\n```js\\nuppy.use(AwsS3, {\\n\\tshouldUseMultipart(file) {\\n\\t\\t// Use multipart only for files larger than 100MiB.\\n\\t\\treturn file.size > 100 * 2 ** 20;\\n\\t},\\n});\\n```\\n\\nor\\n\\n```js\\nuppy.use(AwsS3, {\\n\\tshouldUseMultipart: true,\\n});\\n```\\n\\nPlease see the new\\n[`shouldUseMultipart: boolean | function`](https://uppy.io/docs/aws-s3-multipart/#shouldusemultipartfile)\\noption for details.\\n\\n### Signing on the client\\n\\nBy default, when you upload to S3 with Uppy, every file, or every chunk in case\\nof Multipart, needs to be signed on the server. For many small files or files\\nwith many chunks this means a few additional requests per file/chunk of the\\nupload.\\n\\nTo address this issue and speed up the uploads by roughly 20%, we are\\nintroducing a new option: `getTemporarySecurityCredentials: boolean | function`.\\nWhen `true`, both S3 and S3 Multipart uploads will be signed on the client using\\nthe\\n[AWS Security Federation Token](https://docs.aws.amazon.com/STS/latest/APIReference/API_GetFederationToken.html),\\ncreated once per user (until it expires) on your backend rather than a unique\\nsigned URL for every single chunk.\\n\\n:::caution\\n\\nYou should opt-in into this only if you are comfortable giving end users direct\\naccess to signing files for your bucket.\\n\\n:::\\n\\n### Stability and bug fixes\\n\\n- We\u2019ve improved the internal handling of `RateLimitedQueue` to make\\n [retries more robust](https://github.com/transloadit/uppy/pull/4424) and\\n increased\\n [priority of `abort` and `complete`](https://github.com/transloadit/uppy/pull/4542)\\n requests.\\n- While we were at it, we\u2019ve also fixed\\n [resuming in single-chunk uploads](https://github.com/transloadit/uppy/pull/4528),\\n and improved\\n [chunk size calculation](https://github.com/transloadit/uppy/pull/4508).\\n- [Golden Retriever integration with S3 Multipart](https://github.com/transloadit/uppy/pull/4526)\\n was fixed.\\n\\nAdditionally, we\u2019ve disabled pause-resume buttons in the UI for remote S3\\nMultipart uploads \u2014\xa0they are not supported on Companion, so the UI now reflects\\nthat.\\n\\n## Core\\n\\nPerformance of adding and uploading big batches of files has (yet again) been\\ngreatly improved with refactors in both Uppy Core and Provider Views (that\u2019s\\nwhat we internally call all remote UIs: Instagram, Unsplash, Dropbox).\\n\\nWe\u2019ve been able to achieve this by\\n[refactoring out totals validation for Restrictions (maxTotalFileSize, maxNumberOfFiles)](https://github.com/transloadit/uppy/pull/4402):\\ninstead of doing it for each file, we perform the check at the end, after all\\nthe files have been added/validated. This was confirmed to work with 10k+ files!\\n\ud83d\ude80\\n\\n![\\"Uppy](\\"/img/blog/3.4-3.13/10k-files.jpg\\")
\\n\\nWe\u2019ve also fixed an issue with delayed throttled progress events, which could\\nlead to incorrect progress.\\n\\n## Transloadit\\n\\n### assemblyOptions\\n\\nWe\u2019ve introduced a new option called\\n[`assemblyOptions: object | function`](https://uppy.io/docs/transloadit/#assemblyoptions),\\nwhich replaces the `getAssemblyOptions`, `params` and `fields` (those are now\\ndeprecated and will be removed in the next major).\\n\\nHere\u2019s how you can use the new option as an object:\\n\\n```js\\nuppy.use(Transloadit, {\\n\\tassemblyOptions: {\\n\\t\\tparams: {\\n\\t\\t\\tauth: { key: \'key-from-transloadit\' },\\n\\t\\t\\ttemplate_id: \'id-from-transloadit\',\\n\\t\\t\\tsteps: {\\n\\t\\t\\t\\t// Overruling Template at runtime\\n\\t\\t\\t},\\n\\t\\t},\\n\\t\\tsignature: \'generated-signature\',\\n\\t\\tfields: {\\n\\t\\t\\t// Dynamic or static fields to send along\\n\\t\\t},\\n\\t},\\n});\\n```\\n\\nAnd here\u2019s an example with a function, to be able to set meta fields per-file,\\nfor instance:\\n\\n```js\\nuppy.use(Transloadit, {\\n\\tassemblyOptions(file) {\\n\\t\\treturn {\\n\\t\\t\\tparams: {\\n\\t\\t\\t\\tauth: { key: \'TRANSLOADIT_AUTH_KEY_HERE\' },\\n\\t\\t\\t\\ttemplate_id: \'xyz\',\\n\\t\\t\\t},\\n\\t\\t\\tfields: {\\n\\t\\t\\t\\tcaption: file.meta.caption,\\n\\t\\t\\t},\\n\\t\\t};\\n\\t},\\n});\\n```\\n\\n### Server-sent events\\n\\nHistorically Transloadit supported progress updates via Socket.io. It is a\\nrobust and stable package, but came with a \u201cprice-tag\u201d in the form of bundle\\nsize:\\n[38.3 kB Minified](https://bundlephobia.com/package/socket.io-client@4.7.1). So\\nit\u2019s been on our minds for a while to replace it with something more\\nlightweight, without breaking backwards-compatibility for the older clients (so\\nsimply removing Socket.io on the server in favor of plain WebSockets is not\\ndesireable).\\n\\nThe answer \u2014\\n[Server-sent events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events).\\nIt\u2019s a simple low-overhead one-way connection from Transloadit servers to\\n`@uppy/transloadit`. As was the case with Socket.io, we fall back to HTTP\\npolling every 2 seconds if SSE connection fails for some reason.\\n\\nSocket.io is still around in `@uppy/transloadit`, but will be removed soon, once\\nSSE proves itself in production.\\n\\n### Bug fixes\\n\\n- Reset `tus` key in the file on error, so retried files are re-uploaded.\\n- Clean up event listener to prevent cancelled assemblies.\\n- Make sure `fields` is not nullish when there are no files in Assembly.\\n\\n## Companion\\n\\n### Refresh tokens\\n\\nWe\u2019ve\\n[implemented refresh tokens](https://github.com/transloadit/uppy/pull/4448) for\\nDropbox and Google Drive to solve issued where tokens would expire in the middle\\nof a long upload and then the upload would fail.\\n\\nHere\u2019s how it\u2019s implemented in Companion:\\n\\n- We changed the logic when receiving a 401 from Companion, Uppy will now call a\\n new `/:provider/refresh-token` endpoint which will give uppy a new access\\n token.\\n- `refresh_token` is now stored inside uppy auth token along with `access_token`\\n (encrypted JWT) for providers that give a refresh token (before only\\n `access_token` was stored, now we store both as a `JSON.stringify`\u2019d\\n document).\\n\\n### Bug fixes and improvements\\n\\n- Fixed a bug with non-ASCII metadata crashed Companion. The AWS SDK doesn\u2019t\\n encode metadata by itself, so now we do it in Companion.\\n- Switched from aws-sdk v2 to @aws-sdk/\\\\* v3\\n- Upgraded Grant dependency\\n- We now send expire info for non-multipart uploads and added connection\\n keep-alive to Dropbox to improve connection stability\\n- Merged Provider and SearchProvider internal remote source classes.\\n- Increased max limits for remote file list operations and fixed part listing in\\n S3\\n\\n## Url\\n\\nWe\u2019ve upgraded the Url plugin to use `filename` from `Content-Disposition`\\nheader of the file you are importing, instead of relying on the url (but kept\\nthe latter as a fallback) (#4489). So now your files have proper names instead\\nof `noname`.\\n\\n![\\"Uppy](\\"/img/blog/3.4-3.13/url-name.jpg\\")
\\n\\n## Dashboard and Status Bar\\n\\nSingle File Mode has been improved to adapt to height of less than 400px \u2014 the\\nUI turns back to grid in this case. We are also not using `fit: cover` anymore\\nto avoid cropping important parts of the image:\\n\\n