Arpad Gabor

Seems like the query for the relation select box only returns id's.  The related field looks also empty in the content manager response. (`author` being the field with admin...

@derrickmehaffy I think the first screenshot represents that? My relation is called `authors` and that was the resource it was fetching but only returned the id's.

Yes, I created a test content type. My relation field is called `admin_users` and the content type is `test`. Request: ```http GET /content-manager/relations/api::test.test/1/admin_users?pageSize=5&page=1 HTTP/1.1 Host: localhost:1337 User-Agent: Mozilla/5.0 (Windows NT...

Same issue here. Fixed it with `allowJs: true` in tsconfig, but we're now also seeing "type instantiation is infinitely deep" type of error with Hono, however 1.8.27 works fine.

Experiencing the same problem but on a Windows machine. Linux works fine but when we tried starting an existing project in Windows it crashed with this error after `sst dev`...

Now that also AWS lambda has [support for streaming](https://aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/), are there any plans for supporting streaming out of the box?

@JacobWeisenburger unfortunately that library does not support usage in the browser, and error maps are pretty useful to make internationalized messages.

Relevant issue: https://github.com/JacobWeisenburger/zod_utilz/issues/4. Basically we can't use that helper function to generate the error map as it fails in the browser because they use `process` somewhere. We just copied their...

As the world is (very slowly) moving more into esm, are there any plans on having jiti work with top-level await? [SST](https://sst.dev/) for example uses top-level await to load environment...

Very glad to hear it! Thanks a lot for the follow-up 🤜💥🤛