Should the gradio client build in a default create-react-app out of the box?

[lsb]

Describe the bug

Not sure to file this as a bug or a feature request.

When adding the javascript gradio client, and doing the import { client } from '@gradio/client', to a stock React app, there are lots of build errors with unmet polyfills, like stream, net, tls, buffer, crypto, zlib, zlib_bindings, and more.

It looks like the client is doing interesting things with streaming requests and crypto and such.

I wanted to use the gradio client because I thought I'd read somewhere that the HF spaces with gradio had some queueing logic that the client took care of, and that a Gradio space wasn't just a simple HTTP call for inference.

Should I be able to use the gradio client in a create-react-app app out of the box?

Thanks!

Have you searched existing issues? 🔎

• [X] I have searched and found no existing issues

Reproduction

npx create-react-app gradio-cra-test
cd gradio-cra-test
npm i @gradio/client
echo "import { client } from '@gradio/client'" >> src/App.js
npm run build

Screenshot

No response

Logs

No response

System Info

@gradio/client v0.13.0
node v20.11.1 (lts)
npm 10.2.4
react 18.2.0

Severity

Blocking usage of gradio

[pngwn]

Do you know what bundler cra uses currently?

We are working on the client atm, so I'll add this as a new test case.

[lsb]

CRA uses webpack 5

[marwanelzainy]

Any news on this? Is there a workaround for now?

[pngwn]

Working on it at the minute. Should be addressed shortly.