[rajanpanth]

Summary

• make limit.map use the limiter it belongs to instead of its call-time receiver
• cover detached map calls sharing the limiter's configured concurrency with direct tasks

Problem

LimitFunction.map is exposed as a callable function property, but its implementation invokes the limiter through dynamic this. A valid detached call such as const {map} = limit therefore rejects with TypeError: this is not a function.

Fix

Use the closed-over generator function when scheduling mapped items. This preserves the existing concurrency, ordering, iterable, and index behavior without requiring a bound receiver.

The regression test combines a direct limiter call with a detached map call and verifies their shared maximum concurrency remains at the configured limit.

Testing

• npm exec ava -- --match='map works when detached from the limit'
• npm exec ava
• AVA suite on Node.js 20, 22, and 24
• npm exec tsd
• npm exec xo -- index.js test.js

The aggregate npm test command was also attempted. On this Windows checkout, XO reports its existing TypeScript project-service lookup error for index.d.ts and index.test-d.ts; the same error occurs on the untouched base. The changed JavaScript files pass XO.