Daniel Centore

@Pitouli Are you going to make that PR? I'm also interested in using cloud firestore and this would be super helpful :)

@baba43 @zxl777 I've put together an alternate solution which doesn't use Companion and instead allows you to simply forward all the calls from a NextJS API endpoint https://github.com/daniel-centore/uppy-next-s3-multipart

@lucasbento I was just able to work around this using a ref. I'm using a class component manually assigning like this: ``` // top of the class latestParsedData: React.MutableRefObject; //...

@onrcandan no, I never figured this out. If anyone does figure it out, I would probably revive an old side project of mine...

> You either have to implement the full xattr FUSE functions or disable the xattr support with: -oauto_xattr I had tried to do this but for some reason still couldn't...

> 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...

> You should be able to run any Node.js server in Next.js @Murderlon Doing this eliminates a lot of the benefits of using NextJS. From https://nextjs.org/docs/advanced-features/custom-server : > Before deciding...

For now I'm working around this with: ```typescript import { Body } from "melonjs"; const body = this.body as unknown as Body; // use `body` wherever needed ``` Would be...

I was able to fix this by adding the following line immediately after both of the `$parser = ` lines in `TweekiTemplate.php`: ```php $parser->setOutputType(Parser::OT_HTML); ```

Just wanted to check in an see if anything has happened here. @obukhov-sergey , you seem to have suggested that you've already done this before? Is the code for this...