Balázs Németh

I think this issue might got the `Feature` label by mistake. l tried to bundle the `nuxt` package itself using `rolldown` while working on `obuild` and had this issue again....

@pi0 the issue is with the Nitro build itself, not in a project built with Nitro

Thank you for the explanation, you can find the reproduction here: https://github.com/zsilbi/nitro-mts-repro A temp. fix is to modify `package.json` from `*.d.mts` to `*d.ts` for the runtime entries.

```ts export default cachedEventHandler(async (event) => { console.log(event.waitUntil); // undefined }); ``` When I run this with wrangler it somehow logs `undefined`. Not waiting until the storage finishes writing could...

This would be a very nice improvement! I found this as I was investigating why my noop endpoint latency is so unpredictable. (bottom) 

> Do you recall if we have the same trade-off in v8 based runtimes / Node.js specifically? I ran this again on `node` with the latest benchmark from https://github.com/unjs/ohash/pull/142 (this...

With faster native function check: ```sc ✓ test/benchmarks.bench.ts > benchmarks > serialize - presets > count:128, size:small (with 6 extra functions) 1820ms name hz min max mean p75 p99 p995...

This looks familiar from libraries like https://github.com/ts-rest/ts-rest and https://github.com/unnoq/orpc I think it would be great to make this compatible with these too. I'd personally like if there were: - `headers`...

> This is valid fix thanks but it can cause cache busting (for any current usage) can you checm this? > > In case of changing hashes we should do...