Samuel Cook

I too am seeing `Error: Invalid stdio option "[object EventEmitter]"`. In my case, it is when running nodemon in the package.json `dev` script with `bun --bun run dev`, and the...

Just hit this as well. Beginning of stack trace: ```sh fatal error: concurrent map read and map write goroutine 95 [running]: gorm.io/gorm/callbacks.BuildQuerySQL(0x1400017f830) /Users/sjc/go/pkg/mod/gorm.io/[email protected]/callbacks/query.go:131 +0xc00 gorm.io/gorm/callbacks.Query(0x1400017f830) /Users/sjc/go/pkg/mod/gorm.io/[email protected]/callbacks/query.go:16 +0x38 gorm.io/gorm.(*processor).Execute(0x1400020e2d0, 0x140004e46f0?) /Users/sjc/go/pkg/mod/gorm.io/[email protected]/callbacks.go:130...

I'm seeing this as well when using `c.req.formData()` or `c.req.parseBody()` (which uses the `formData` method under the hood). I suspect it may be related to this: https://github.com/orgs/vercel/discussions/1426

Update, it turns out you need to add `NODEJS_HELPERS=0` to your environment variables, then Hono will work in Vercel serverless (AWS Lambda) See https://vercel.com/docs/functions/serverless-functions/runtimes/node-js#disabling-helpers-for-node.js

> I'm still having trouble. I'll get a 500 response on any `post` method when adding a JSON payload (locally). It would be nice to see a complete working example...

Is there another task for the "always" eslint setting (i.e., requiring you to add explicit block and return statement)? If not, it would be nice if the title of this...

> We could use a name such as `useConsistentArrowReturn`. I think that name works even if we add the option. I like that, and it seems to align with other...

Hey there @Marcisbee, Thanks! I'm not very familiar with Pocketbase, but it would be a great thing to try to get working. I don't see any reason why that wouldn't...

@river-now uses this option as well (set to `exports-only`). That said, as long as we set `ROLLDOWN_OPTIONS_VALIDATION=loose`, everything still seems to work with the current vite-rolldown behavior.