Lock lru-cache to 11.2.7 (11.3.0 breaks due to top-level await on ES …

[npc-nathan]

Upgrading lru-cache to "11.3.0" breaks due to top-level await on ES Module Entry Point. Locking to "11.2.7" allows it build and run successfully.

[coderabbitai]

📝 Walkthrough

Walkthrough

The lru-cache devDependency version specification in package.json was changed from a caret range (^11.2.7) to an exact pinned version (11.2.7), preventing automatic minor and patch version updates during dependency resolution.

Changes

Cohort / File(s)	Summary
Dependency Version Lock package.json	Changed lru-cache devDependency from caret range ^11.2.7 to exact version 11.2.7, preventing automatic minor/patch upgrades.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version pinned, so firm and true,
No surprises from the caret crew,
Eleven point two point seven stays,
Through all our testing nights and days! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: locking lru-cache to version 11.2.7 to avoid breakage from version 11.3.0's top-level await issue.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}