Isolate cache per doc loader and add cache instance option.

CHANGELOG.md

@@ -1,5 +1,15 @@
 # security-document-loader Changelog
 
+## 3.2.0 - 2026-mm-dd
+
+### Added
+- Use `@digitalbazaar/did-io@2.1` in order to allow passing in a particular
+  LRU cache instance when creating a security document loader instance. Each
+  security loader instance will use its own `CachedResolver` to resolve
+  DIDs. The new `cache` parameter is optional, and if used, must specify
+  an `LruCache` instance from `@digitalbazaar/lru-memoize@4` or an instance
+  that includes, minimally, a compatible `memoize()` function.
+
 ## 3.1.0 - 2025-09-21
 
 ### Changed

lib/security-loader.js

@@ -1,5 +1,5 @@
 /*!
- * Copyright (c) 2021-2025 Digital Bazaar, Inc. All rights reserved.
+ * Copyright (c) 2021-2026 Digital Bazaar, Inc. All rights reserved.
  */
 import {CachedResolver} from '@digitalbazaar/did-io';
 import {driver} from '@digitalbazaar/did-method-key';
@@ -17,12 +17,13 @@ didKeyDriver.use({
   multibaseMultikeyHeader: 'z6Mk',
   fromMultibase: Ed25519VerificationKey2020.from
 });
-const resolver = new CachedResolver();
-resolver.use(didKeyDriver);
 
 import {JsonLdDocumentLoader} from 'jsonld-document-loader';
 
-export function securityLoader() {
+export function securityLoader({cache} = {}) {
+  const resolver = new CachedResolver({cache});
+  resolver.use(didKeyDriver);
+
   const loader = new JsonLdDocumentLoader();
 
   loader.addDocuments({documents: [

package.json

@@ -24,7 +24,7 @@
   ],
   "dependencies": {
     "@digitalbazaar/credentials-context": "^3.2.0",
-    "@digitalbazaar/did-io": "^2.0.0",
+    "@digitalbazaar/did-io": "^2.1.0",
     "@digitalbazaar/did-method-key": "^5.3.0",
     "@digitalbazaar/ed25519-verification-key-2020": "^4.2.0",
     "did-context": "^3.1.1",