apostrophe-caches-redis - npm Package Compare versions

Comparing version 2.1.1 to 2.1.2

CHANGELOG.md

 # Changelog
 
+* 2.1.2 fixes a bug where `ensureIndexes()` in `apostrophe-caches` was attempting to create new indexes where mongo was not being used.
+
 * 2.1.1: `apos.destroy` now closes the Redis connection, for compatibility with
@@ -7,4 +9,4 @@ `apostrophe-monitor` and `apostrophe-multisite`. Corrections were made to the
 `mocha` 5.x is used, addressing reported vulnerabilities from `npm audit`,
-although in actuality the vulnerable modules were only used by the test runner. 
+although in actuality the vulnerable modules were only used by the test runner.
 
 * 2.1.0: promise support. The `get`, `set` and `clear` methods of caches now return promises if no callback is given, matching the behavior of Apostrophe's core cache.

index.js

@@ -31,2 +31,8 @@ // TODO:
 
+    // Override the ensureIndexes method, which is not needed since we are
+    // not using mongo collections.
+    self.ensureIndexes = function(callback) {
+      return callback(null);
+    }
+
     self.constructCache = function(name) {
@@ -143,2 +149,1 @@
 };
-

package.json

 {
   "name": "apostrophe-caches-redis",
-  "version": "2.1.1",
+  "version": "2.1.2",
   "description": "Redis-based cache for the Apostrophe CMS",
@@ -5,0 +5,0 @@ "main": "index.js",

New alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

13649

increased by2.46%

Lines of code

338

increased by1.5%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

No dependency changes