Johannes Zellner

Actually using the following resolution for yarn, does indeed work as expected: ``` "resolutions": { "*/jquery": "3.6.0" } ``` I guess this can be closed then, an `yarn` support at...

Seems like adding the wildcard on the jquery version side, `yarn` will again install different `jquery` versions like `3.6.0` and `3.6.1` leading to the same `webpack` bundling issue as initially.

Is there any update on that, as I also just hit that unfortunately.

Came here to ask if `APP_NEW_FETCHING_LIBRARY=true` is considered stable for a good default by now? Asking since a Cloudron user fixed issues on his instance with it and we were...

Came here to report that the app kept redirecting to localhost:3000 and this is probably the reason then. The Cloudron package is built without a final domain, as it is...

hm I see this issue is much older. Well it was detected by our tests, so I started investigation. Maybe then it is related to https://github.com/lukevella/rallly/commit/703d551aac7647b46039a05fd06662bec0d758a9 ?

Last working version was 3.1.0 so possibly then I am chasing the wrong thing. I see that the `process.env.` usage was always like that so always during the build?

Maybe should split this into a new issue then. Also we had to apply the same fix exporting `HOSTNAME` as we had to for https://github.com/baptisteArno/typebot.io/issues/911#issuecomment-1761210931 possibly then some nextjs update...

Tried to get the app working locally to reproduce the issue, but didn't succeed to get it working at all there. So I went to bisect it via a Cloudron...

Ah right, should have seen that start script change earlier. Have triggered a new test run with it now, so if that works its fine, no need to change this...