handy-redis - npm Package Compare versions

Comparing version 1.8.1 to 1.8.2

dist/index.js

		@@ -7,3 +7,3 @@ "use strict";
		exports.createHandyClient = (...clientArgs) => {
		const nodeRedis = (typeof clientArgs[0] === "object" && typeof clientArgs[0].zscan === "function")
		const nodeRedis = (typeof clientArgs[0] === "object" && typeof clientArgs[0].scan === "function")
		? clientArgs[0]
		@@ -10,0 +10,0 @@ : redis_1.createClient.apply(null, clientArgs);

package.json

		{
		"name": "handy-redis",
		"version": "1.8.1",
		"version": "1.8.2",
		"description": "A wrapper around node_redis with Promise and TypeScript support.",
		@@ -28,4 +28,4 @@ "main": "dist/index.js",
		"release": "semantic-release",
		"coverage": "npm run test -- --coverage",
		"coveralls": "npm run coverage -- --coverageReporters=text-lcov \| coveralls"
		"coverage": "yarn test --coverage",
		"coveralls": "yarn coverage --coverageReporters=text-lcov \| coveralls"
		},
		@@ -77,2 +77,3 @@ "repository": {
		"@types/node": "^12.12.37",
		"@types/redis-mock": "^0.17.0",
		"@types/shelljs": "^0.8.5",
		@@ -90,2 +91,3 @@ "@types/yamljs": "^0.2.30",
		"redis-commands": "^1.5.0",
		"redis-mock": "^0.49.0",
		"semantic-release": "^15.13.16",
		@@ -92,0 +94,0 @@ "shelljs": "^0.8.3",

README.md

		@@ -85,3 +85,3 @@ # handy-redis
		```
		Then in a separate terminal, make sure you have docker installed and `docker-compose` is on your path, and start up a redis server in the background with `npm run redis:up`.
		Then in a separate terminal, make sure you have docker installed and `docker-compose` is on your path, and start up a redis server in the background with `yarn redis:up`.

		@@ -91,6 +91,6 @@ To fully test the package as it is on your machine, the same way travis does:
		```cli
		npm run ci
		yarn ci
		```

		`npm run ci` runs the build, test and lint scripts. It removes all generated code before, and after checks that your git status is clean. This is to allow tracking changes to the generated client over time, to make what the published package contains more visible, and to make sure that generated code hasn't been modified without auditing first. You should not manually edit any files under a `/generated/` path. If `npm run ci` fails for you because you deliberately changed the way the codegen works, take a look at the git changes, check them in and run `npm run ci` again.
		`yarn ci` runs the build, test and lint scripts. It removes all generated code before, and after checks that your git status is clean. This is to allow tracking changes to the generated client over time, to make what the published package contains more visible, and to make sure that generated code hasn't been modified without auditing first. You should not manually edit any files under a `/generated/` path. If `yarn ci` fails for you because you deliberately changed the way the codegen works, take a look at the git changes, check them in and run `yarn ci` again.

		@@ -97,0 +97,0 @@ The `build` script generates the client before using TypeScript to compile it. If you want to run the tests without rebuilding, use `npm test`.

handy-redis - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics

Worsened metrics