@visulima/connect 1.1.1 → 1.3.0

package/CHANGELOG.md

@@ -1,3 +1,17 @@
+## @visulima/connect [1.3.0](https://github.com/visulima/visulima/compare/@visulima/connect@1.2.0...@visulima/connect@1.3.0) (2022-11-16)
+
+
+### Features
+
+* **health-check:** adding new health-check package ([#17](https://github.com/visulima/visulima/issues/17)) ([2e2a89f](https://github.com/visulima/visulima/commit/2e2a89fe85214237c9f55bf00d76b69de691ee3e))
+
+## @visulima/connect [1.2.0](https://github.com/visulima/visulima/compare/@visulima/connect@1.1.1...@visulima/connect@1.2.0) (2022-11-15)
+
+
+### Features
+
+* added new packages for faster api creation ([#14](https://github.com/visulima/visulima/issues/14)) ([eb64fcf](https://github.com/visulima/visulima/commit/eb64fcf33f2a75ea48262ad6e71f80e159a93972))
+
 ## @visulima/connect [1.1.1](https://github.com/visulima/visulima/compare/@visulima/connect@1.1.0...@visulima/connect@1.1.1) (2022-11-09)
 
 

package/README.md

@@ -59,7 +59,7 @@ pnpm add @visulima/connect
 >
 > Although `@visulima/connect` is initially written for Next.js, it can be used in [http server](https://nodejs.org/api/http.html#httpcreateserveroptions-requestlistener), [Vercel](https://vercel.com/docs/concepts/functions/serverless-functions). See [Examples](./examples/) for more integrations.
 
-Below are some use cases.
+Below are use cases.
 
 ### Next.js API Routes
 
@@ -415,7 +415,7 @@ await router.run(req, res);
 
 ## Common errors
 
-There are some pitfalls in using `@visulima/connect`. Below are things to keep in mind to use it correctly.
+There are pitfalls in using `@visulima/connect`. Below are things to keep in mind to use it correctly.
 
 1. **Always** `await next()`
 
@@ -603,7 +603,7 @@ router.use(expressWrapper(someExpressMiddleware));
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
+[Node.js’ release schedule](https://github.com/nodejs/release#release-schedule). Here’s [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 ## Contributing

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@visulima/connect",
-    "version": "1.1.1",
+    "version": "1.3.0",
     "description": "The minimal router and middleware layer for Next.js, Micro, Vercel, or Node.js http/http2 with support for zod validation.",
     "keywords": [
         "javascript",
@@ -64,7 +64,7 @@
         "clean": "rimraf node_modules dist",
         "coverage": "vitest run --coverage",
         "dev": "pnpm predev && pnpm run build --watch",
-        "lint:eslint": "cross-env NO_LOGS=true eslint --ext js,jsx,ts,tsx --max-warnings=0 --config .eslintrc.cjs --cache --cache-strategy content .",
+        "lint:eslint": "cross-env NO_LOGS=true eslint --ext js,jsx,ts,tsx --max-warnings=0 --config .eslintrc.cjs",
         "lint:eslint:fix": "pnpm run lint:eslint --fix",
         "test": "vitest"
     },