Pooya Parsa
Pooya Parsa
Thank you for the PR and sorry for late review. I have added a dep reproduction and it fixes issue. Testing on some projects, I found effect of this change...
Thank you! Perhaps better call it more explicitly `transformClassProps` ?
I think we would never enable this by default, as it implies more transformation and less proximity to runtime native behavior .
Yes generic opt-in flag is cool 👍🏼 (my goal for jiti is to be as close to native Node.js as possible by default.)
Jiti supports all of those (TS features). I meant runtime (JS) syntax support like class props. It can be easily an opt in feature for when needed for class props...
@danielroe Is this something you plan to work on?
Thanks for issue. We should introduce a way to allow reconnecting instances indeed.
Thanks for nice work and suggstion. I have updated org, this repository needs little bit maintenance first.
I think this might be rather an enahcenment to introduce: - Add options to allow limiting how much data to read - We might also consider supporting it in Nitro...
upcoming H3 v2 is based on web apis. Using `event.request.body` in Node.js also initiates a `ReadableStream` suitable for handling larger payloads.