Artur Paikin

Just faced this again when trying to use `preact/hooks` in a new module in uppy.io, we had to patch Preact in uppy again: https://github.com/transloadit/uppy/pull/4283/commits/11f1476edae5a0bacb43df3e5025906bd0b0a93d.

Uppy is actively maintained :) There are integrations for React, Vue, Svetle, etc. I am not sure how we can better support Next.js. Companion is meant to be run standalone...

@daniel-centore thanks for the clarification! Why not run Companion standalone and call its APIs from NextJS, what is the benefit of making Companion part of your NextJS app?

@altechzilla because Companion is a relatively complex standalone proxy server that handles oauth for Google Drive, Instagram, Dropbox, etc + file signing and uploading for XHR, S3 and tus protocols....

We have internal, non-documented: - `plugin-added` - `plugin-removed`

Hi! Thanks for the PR. I'd rather handle it differently, probably forgoing the `` altogether or using `uppy-u-reset` class. In most places in Uppy I've purposefully removed semantic typography elements...

@Acconut: > After reading through https://stackoverflow.com/questions/1957115/is-a-slash-equivalent-to-an-encoded-slash-2f-in-the-path-portion-of-a and doing some tests with curl and Firefox, it is technically possible to encode the upload ID. So the upload ID hello/world would then...

@rquinlivan Yeah, much appreciated, thanks! But we were thinking we still need to safeguard against such cases internally.