Adicco Bhikkhu

To fix my particular issue one can use typebox's ```additionalProperties```: ```ts params: t.Object({ item_id: t.String() }, { additionalProperties: true }) ``` But I am still wondering if there might be...

Same issue here, the [example](https://github.com/elysiajs/elysia-jwt/blob/main/example/index.ts) actually raises a TS error on 'jwt' at `.get('/sign/:name', async ({ jwt, cookie, setCookie, params }) =>`

@rolznz Use [serverComponentsExternalPackages](https://beta.nextjs.org/docs/api-reference/next-config#servercomponentsexternalpackages) in next.config.js, e.g.: ```js /** @type {import('next').NextConfig} */ const nextConfig = { reactStrictMode: true, experimental: { serverComponentsExternalPackages: ['bullmq'] } } module.exports = nextConfig ```

Also noticed a regression with afterSettle and afterSwap events, which are not firing on 2.0.0 (it works straight away on 1.9.12 if I revert to it.) However, for me it...

Maybe related, the `html` plugin seems to be throwing a type error I did not encounter before, but could be related to a recent `bun update` ``` No overload matches...

(and I am also having issues with my `afterHandle` handlers not being executed)

I would also expect a local afterHandle to run, rather than having to guess which global plugin exited early.