Jems

I have this problem as well. Is there a workaround?

This might fix the problem when vue 3.3 is out: https://github.com/vuejs/core/commit/4b5b384485cf8f6124f6738b89e3d047358f3a11 https://github.com/vuejs/core/commit/94fa67a4f73b3646c8c1e29512a71b17bd56efc3

I'm a bit confused by the timeline but it has been fixed in [this PR](https://github.com/api-platform/create-client/pull/98)

Soon @gurnro You can check [this MR](https://github.com/dunglas/react-esi/pull/61) which improve on the previous one that added the React and Next examples directly into the repository.

Yes we can but I'm wondering if we could just use the name of the field instead of the reference name or embedded name. This issue is also present in...

In fact, the one I was the most interested in is lz-string. I'll look into it, thank you very much!

Hello @misterx, Thank you for bringing this to our attention. We plan to address this issue in an upcoming release. Please stay tuned for updates!

Are there any updates on this issue?

Hello @JDruery, Thank you for reporting this issue. The problem you're encountering during the production build appears to be related to the Next.js client's inability to access the API, which...

I've updated my initial post due to additional issues encountered during runtime. For the API and Mercure to function correctly without HTTPS, it's necessary to revise the TRUSTED_HOSTS and MERCURE_PUBLIC_URL...