Fix: Correct AsyncLocalStorage type parameter to match actual store

[gleb-lobastov]

Fix: Correct AsyncLocalStorage type parameter to match actual store (RequestContextData)

The AsyncLocalStorage was incorrectly typed as RequestContext, but in reality it stores RequestContextData, which is directly accessed via key-value operations (e.g. store[key]).

Checklist

• [ + ] run npm run test and npm run benchmark
• [ - ] tests and/or benchmarks are included
• [ - ] documentation is changed or added
• [ + ] commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[mcollina]

lgtm

[gurgunday]

lgtm

[Copilot]

Pull Request Overview

This PR fixes a type inconsistency in the AsyncLocalStorage type parameter. The AsyncLocalStorage was incorrectly typed as storing RequestContext when it actually stores RequestContextData.

• Corrects the AsyncLocalStorage type parameter from RequestContext to RequestContextData
• Updates type test to properly validate the AsyncLocalStorage stores RequestContextData

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.}

[tobiasdcl]

It would be great if this could be merged 🙌

I ran into this exact problem while following the Usage outside of a request as described in the readme:

import { asyncLocalStorage } from '@fastify/request-context';

it('should set request context', () => {
  asyncLocalStorage.run({}, async () => {
    requestContext.set('userId', 'some-fake-user-id');
    someCodeThatUsesRequestContext(); // requestContext.get('userId') will work
  })
})

results in TS error:

Argument of type '{}' is not assignable to parameter of type 'RequestContext'.
      Type '{}' is missing the following properties from type 'RequestContext': get, set, getStore

[Tony133]

@gleb-lobastov as soon as you have time, can you resolve the conflicts?