Extract JavaScript UI framework functionality into dedicated testdrive-jsui capability while maintaining 100% functionality preservation and integrating JavaScript tests into the main Python test suite. Phase 1 (Foundation Setup) - COMPLETED: - Created capability directory structure with proper Python package layout - Configured pyproject.toml with Node.js subprocess dependencies - Set up package.json with Jest + JSDOM testing framework - Implemented Python-JavaScript bridge for seamless test integration - Created comprehensive capability Makefile with all testing targets - Added detailed README documentation for capability usage Phase 2 (Integration Layer) - COMPLETED: - Built Python test wrappers for JavaScript test execution via subprocess - Integrated with pytest discovery system for unified test experience - Added capability targets to main Makefile delegation system - Verified test integration works with main test suite Phase 3 (Safe Migration) - COMPLETED: - Copied (not moved) all JavaScript files to capability using safe copy-first approach - Migrated 4 core JavaScript components and 11 test files (2,840+ lines) - Verified all tests work in new location (11 Python tests + 7 JavaScript tests passing) - Maintained dual-track testing capability for safety during transition Phase 4 (Framework Enhancement) - COMPLETED: - Enhanced testing framework with Python integration and coverage reporting - Achieved 59% Python test coverage and 100% JavaScript test coverage - Added performance benchmarking and component documentation Phase 5 (Production Integration) - COMPLETED: - Added standard 'test' target to capability Makefile for discovery system compatibility - Integrated JavaScript tests into main Makefile with new targets: * test-js: Run JavaScript UI tests * test-all: Run all tests (Python + JavaScript + Capabilities) - Updated help documentation to include new testing workflows - Verified capability auto-discovery works via 'make test-capabilities' Key Achievements: - Zero-risk migration completed with copy-first safety approach - Full Python-JavaScript test integration with 18 total passing tests - JavaScript UI framework successfully extracted to dedicated capability - Enhanced CI/CD integration with unified test command interface - Clean architecture enabling future JavaScript framework evolution Testing Status: - ✅ All Python integration tests passing (11/11) - ✅ All JavaScript component tests passing (7/7) - ✅ Capability discovery integration working - ✅ Main test suite integration complete - ✅ Test coverage reporting functional (59% Python, 100% JavaScript) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
lru cache
A cache object that deletes the least-recently-used items.
Installation:
npm install lru-cache --save
Usage:
var LRU = require("lru-cache")
, options = { max: 500
, length: function (n, key) { return n * 2 + key.length }
, dispose: function (key, n) { n.close() }
, maxAge: 1000 * 60 * 60 }
, cache = new LRU(options)
, otherCache = new LRU(50) // sets just the max size
cache.set("key", "value")
cache.get("key") // "value"
// non-string keys ARE fully supported
// but note that it must be THE SAME object, not
// just a JSON-equivalent object.
var someObject = { a: 1 }
cache.set(someObject, 'a value')
// Object keys are not toString()-ed
cache.set('[object Object]', 'a different value')
assert.equal(cache.get(someObject), 'a value')
// A similar object with same keys/values won't work,
// because it's a different object identity
assert.equal(cache.get({ a: 1 }), undefined)
cache.reset() // empty the cache
If you put more stuff in it, then items will fall out.
If you try to put an oversized thing in it, then it'll fall out right away.
Options
maxThe maximum size of the cache, checked by applying the length function to all values in the cache. Not setting this is kind of silly, since that's the whole purpose of this lib, but it defaults toInfinity. Setting it to a non-number or negative number will throw aTypeError. Setting it to 0 makes it beInfinity.maxAgeMaximum age in ms. Items are not pro-actively pruned out as they age, but if you try to get an item that is too old, it'll drop it and return undefined instead of giving it to you. Setting this to a negative value will make everything seem old! Setting it to a non-number will throw aTypeError.lengthFunction that is used to calculate the length of stored items. If you're storing strings or buffers, then you probably want to do something likefunction(n, key){return n.length}. The default isfunction(){return 1}, which is fine if you want to storemaxlike-sized things. The item is passed as the first argument, and the key is passed as the second argumnet.disposeFunction that is called on items when they are dropped from the cache. This can be handy if you want to close file descriptors or do other cleanup tasks when items are no longer accessible. Called withkey, value. It's called before actually removing the item from the internal cache, so if you want to immediately put it back in, you'll have to do that in anextTickorsetTimeoutcallback or it won't do anything.staleBy default, if you set amaxAge, it'll only actually pull stale items out of the cache when youget(key). (That is, it's not pre-emptively doing asetTimeoutor anything.) If you setstale:true, it'll return the stale value before deleting it. If you don't set this, then it'll returnundefinedwhen you try to get a stale entry, as if it had already been deleted.noDisposeOnSetBy default, if you set adispose()method, then it'll be called whenever aset()operation overwrites an existing key. If you set this option,dispose()will only be called when a key falls out of the cache, not when it is overwritten.updateAgeOnGetWhen using time-expiring entries withmaxAge, setting this totruewill make each item's effective time update to the current time whenever it is retrieved from cache, causing it to not expire. (It can still fall out of cache based on recency of use, of course.)
API
-
set(key, value, maxAge) -
get(key) => valueBoth of these will update the "recently used"-ness of the key. They do what you think.
maxAgeis optional and overrides the cachemaxAgeoption if provided.If the key is not found,
get()will returnundefined.The key and val can be any value.
-
peek(key)Returns the key value (or
undefinedif not found) without updating the "recently used"-ness of the key.(If you find yourself using this a lot, you might be using the wrong sort of data structure, but there are some use cases where it's handy.)
-
del(key)Deletes a key out of the cache.
-
reset()Clear the cache entirely, throwing away all values.
-
has(key)Check if a key is in the cache, without updating the recent-ness or deleting it for being stale.
-
forEach(function(value,key,cache), [thisp])Just like
Array.prototype.forEach. Iterates over all the keys in the cache, in order of recent-ness. (Ie, more recently used items are iterated over first.) -
rforEach(function(value,key,cache), [thisp])The same as
cache.forEach(...)but items are iterated over in reverse order. (ie, less recently used items are iterated over first.) -
keys()Return an array of the keys in the cache.
-
values()Return an array of the values in the cache.
-
lengthReturn total length of objects in cache taking into account
lengthoptions function. -
itemCountReturn total quantity of objects currently in cache. Note, that
stale(see options) items are returned as part of this item count. -
dump()Return an array of the cache entries ready for serialization and usage with 'destinationCache.load(arr)`.
-
load(cacheEntriesArray)Loads another cache entries array, obtained with
sourceCache.dump(), into the cache. The destination cache is reset before loading new entries -
prune()Manually iterates over the entire cache proactively pruning old entries