Invalid onAfterResponse typing

[nxht]

What version of Elysia is running?

1.1.13

What platform is your computer?

Linux 5.15.153.1-microsoft-standard-WSL2 x86_64 x86_64

What steps can reproduce the bug?

import Elysia from 'elysia';

const app = new Elysia()
  .onAfterResponse((ctx) => {
    ctx.request;
  })

What is the expected behavior?

ctx is typed correctly and ctx.request exists

What do you see instead?

ctx is inferred as never in typescript

Additional information

Same issue doesn't happen on 1.1.12. Might be related with #810

Have you try removing the node_modules and bun.lockb and try again yet?

Yes

[bompus]

I commented on a commit actually, but I don't think the author saw it. It appears the unit test for this was commented out, so the regression wasn't caught.

elysia/test/types/index.ts

Line 1969 in 6109684

// expectTypeOf<typeof params>().toEqualTypeOf<Record<string, string>>()

[7f8ddd]

It's also only in the plugin itself, any plugins that use it will have types.

[nathankleyn]

We also have this exact same issue from 1.1.13 onwards. In our case, it's a logging "middleware" where all of the params to .onAfterResponse now type as never:

return new Elysia({
  name: "logger",
})
  .derive(() => {
    return {
      startTime: performance.now(),
    };
  })
  .onAfterResponse({ as: "global" }, ({ request, set, startTime }) => {
    // request, set and startTime are all `never`
  });

[crishoj]

Wrong types with 1.1.16 too:

[ghost]

same here

[7f8ddd]

@SaltyAom We gonna have beef real soon if you don't stop watching anime girls and fix this, on folk n em