Implement in-memory cache for modules #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎯 Summary
Implements in-memory caching for modules to significantly improve performance by avoiding redundant file operations, as requested in issue #27.
📋 Changes Made
moduleCacheMap to store imported modules by their resolved pathbuiltinCacheMap to cache built-in modules by module:environment keytests/cache.test.mjswith 5 test cases covering different caching scenariosexamples/cache-demo.mjsto demonstrate caching performance improvements🧪 Test Coverage
All new caching functionality is thoroughly tested:
node:prefixed imports🔧 Technical Implementation
Module Caching
Built-in Module Caching
🚀 Performance Impact
📁 Files Modified
use.mjs- Added caching to module and built-in resolversuse.js- Applied same caching changes for browser compatibilityuse.cjs- Applied same caching changes for CommonJS compatibilitytests/cache.test.mjs- New comprehensive test suiteexamples/cache-demo.mjs- New demo scriptFixes #27
🤖 Generated with Claude Code