feat: add named export for memory store

[gamemaker1]

Related Issues

• Closes Expose MemoryStore as a named export #289

What Does This PR Do?

Added

• Added a named export for the MemoryStore class.

Checklist

• The issues that this PR fixes/closes have been mentioned above.
• What this PR adds/changes/removes has been explained.
• All tests (npm test) pass.
• All added/modified code has been commented, and
  methods/classes/constants/types have been annotated with TSDoc comments.
• If a new feature has been added or a bug has been fixed, tests have been
  added for the same.

[nfriedly]

LGTM!

That esbuild --footer is getting a little hairy, but I don't think there's a better option right now.

[gamemaker1]

That esbuild --footer is getting a little hairy, but I don't think there's a better option right now.

That's bugging me too 😬. Maybe we can use esbuild's __toCommonJSExport function there instead of the module.export.{default, rateLimit,Memory store}?

[nfriedly]

Yeah... ideally I'd like to see a new flag in ES build that controls the default export behavior for cjs, rather than us having to continue hacking around it.

[gamemaker1]

Maybe we can use ESBuild's __toCommonJSExport function there instead of the module.export.{default, rateLimit,Memory store}

That didn't work - Jest could not resolve named imports in the JS-ESM import tests when I did that. Merging with the big footer for now.

[gamemaker1]

Should I release v6.2.0 - it will include this as well as the deprecate onLimitReached fixes.

[nfriedly]

Yeah, go ahead :)