handy-redis - npm Package Compare versions

Comparing version 2.2.0 to 2.2.1

package.json

 {
   "name": "handy-redis",
-  "version": "2.2.0",
+  "version": "2.2.1",
   "description": "A redis client with first-class Promise and TypeScript support, and extensive documentation.",
@@ -38,3 +38,2 @@ "keywords": [
     "check-clean": "check-clean",
-    "ci": "run-s clean build coverage lint check-clean",
     "preclean": "del-cli temp/backup-test-generated && mkdir -p temp && cp -r test/generated temp/backup-test-generated",
@@ -45,4 +44,5 @@ "clean": "del-cli 'dist' 'ts34' 'src/generated' 'test/generated'",
     "postcompile": "node downlevel",
-    "coverage": "yarn test --coverage",
+    "coverage": "yarn jest --coverage",
     "coveralls": "yarn coverage --coverageReporters=text-lcov | coveralls",
+    "jest": "jest --runInBand --forceExit --detectOpenHandles",
     "lint": "eslint --max-warnings 0 --ext .ts,.js,.md .",
@@ -54,3 +54,3 @@ "redis-cli": "docker-compose exec redis redis-cli",
     "release": "semantic-release",
-    "test": "jest --runInBand --forceExit --detectOpenHandles",
+    "test": "run-s clean build coverage lint check-clean",
     "tsn": "ts-node --transpile-only",
@@ -81,3 +81,3 @@ "typecheck": "tsc -p ."
     "eslint-plugin-prettier": "3.3.0",
-    "eslint-plugin-unicorn": "24.0.0",
+    "eslint-plugin-unicorn": "25.0.1",
     "expect-type": "0.11.0",
@@ -84,0 +84,0 @@ "fs-syncer": "0.3.4-next.1",

README.md

@@ -160,8 +160,8 @@ # handy-redis
 ```cli
-yarn ci
+yarn test
 ```
 
-`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.
+`yarn test` 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 test` 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 test` again.
 
-The `build` script generates the client before using TypeScript to compile it. If you want to run the tests without rebuilding, use `npm test`.
+The `build` script generates the client before using TypeScript to compile it. If you want to run the tests without rebuilding, linting etc., use `yarn jest`.
 
@@ -178,4 +178,4 @@ There are some more scripts in `package.json` which can be useful for local development.
 
-If a snapshot test fails, it's possible it just needs to be updated. Make sure your git status is clean and run `yarn test -u`.
+If a snapshot test fails, it's possible it just needs to be updated. Make sure your git status is clean and run `yarn jest -u`.
 
 Types are tested using [expect-type](https://npmjs.com/package/expect-type).

No alert changes

Worsened metrics

Total package byte prevSize

700094

decreased by-66.09%

Number of package files

30

decreased by-21.05%

Lines of code

14092

decreased by-66.26%

No dependency changes