Meowster

I know that my english may be far from ideal 😺

https://github.com/oven-sh/bun/issues/1805

[Svelte native REPL](https://svelte-native.technology/repl?example=hello-world) works well.

I managed to publish my library on JSR from bun monorepo https://github.com/MeowningMaster/wsx https://jsr.io/@wsx

- There is no need in additional instance config for something that can be expressed as a plugin. - `store` is a global state of the server shared across all...

I support deprecation of eden treaty. It feels harder to read and compose The only problem for me is feature parity. As far as I know eden fetch does not...

Does not infer them for me too. I see that Elysia instance properly stores it in `~Routes` property type. So it's either problem with [unpacking them in `Treaty.Create`](https://github.com/elysiajs/eden/blob/72a04721ed2953f95f3a3159af473699cb4057ad/src/treaty2/types.ts#L93-L108). Or mismatch...

Also please intersect inferred headers type with `Record` (or any other `HeaderInit`-ish type that you support) so it's possible to pass arbitrary additional headers to request

JSON/JSONB serialization/deserialization is fixed in Bun 1.3 https://github.com/oven-sh/bun/pull/22700 So i'm using this custom column: ```ts import { customType } from 'drizzle-orm/pg-core' // Bun serializes and deserializes JSONB internally export const...

Problem with `jsonb` implementation built in to drizzle-orm still exists. Both for Bun.SQL and Postgres.js. They have their own serialization/deserialization and when processed by https://github.com/drizzle-team/drizzle-orm/blob/a9136ee2df9616fef059cf398bea486da23faa47/drizzle-orm/src/pg-core/columns/jsonb.ts#L42-L56 some weird edge cases emerge:...