@visulima/connect 1.1.1 → 1.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +7 -0
- package/README.md +3 -3
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,10 @@
|
|
|
1
|
+
## @visulima/connect [1.2.0](https://github.com/visulima/visulima/compare/@visulima/connect@1.1.1...@visulima/connect@1.2.0) (2022-11-15)
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
### Features
|
|
5
|
+
|
|
6
|
+
* added new packages for faster api creation ([#14](https://github.com/visulima/visulima/issues/14)) ([eb64fcf](https://github.com/visulima/visulima/commit/eb64fcf33f2a75ea48262ad6e71f80e159a93972))
|
|
7
|
+
|
|
1
8
|
## @visulima/connect [1.1.1](https://github.com/visulima/visulima/compare/@visulima/connect@1.1.0...@visulima/connect@1.1.1) (2022-11-09)
|
|
2
9
|
|
|
3
10
|
|
package/README.md
CHANGED
|
@@ -59,7 +59,7 @@ pnpm add @visulima/connect
|
|
|
59
59
|
>
|
|
60
60
|
> 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.
|
|
61
61
|
|
|
62
|
-
Below are
|
|
62
|
+
Below are use cases.
|
|
63
63
|
|
|
64
64
|
### Next.js API Routes
|
|
65
65
|
|
|
@@ -415,7 +415,7 @@ await router.run(req, res);
|
|
|
415
415
|
|
|
416
416
|
## Common errors
|
|
417
417
|
|
|
418
|
-
There are
|
|
418
|
+
There are pitfalls in using `@visulima/connect`. Below are things to keep in mind to use it correctly.
|
|
419
419
|
|
|
420
420
|
1. **Always** `await next()`
|
|
421
421
|
|
|
@@ -603,7 +603,7 @@ router.use(expressWrapper(someExpressMiddleware));
|
|
|
603
603
|
## Supported Node.js Versions
|
|
604
604
|
|
|
605
605
|
Libraries in this ecosystem make the best effort to track
|
|
606
|
-
[Node.js
|
|
606
|
+
[Node.js’ release schedule](https://github.com/nodejs/release#release-schedule). Here’s [a
|
|
607
607
|
post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
|
|
608
608
|
|
|
609
609
|
## Contributing
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@visulima/connect",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.2.0",
|
|
4
4
|
"description": "The minimal router and middleware layer for Next.js, Micro, Vercel, or Node.js http/http2 with support for zod validation.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"javascript",
|
|
@@ -64,7 +64,7 @@
|
|
|
64
64
|
"clean": "rimraf node_modules dist",
|
|
65
65
|
"coverage": "vitest run --coverage",
|
|
66
66
|
"dev": "pnpm predev && pnpm run build --watch",
|
|
67
|
-
"lint:eslint": "cross-env NO_LOGS=true eslint --ext js,jsx,ts,tsx --max-warnings=0 --config .eslintrc.cjs
|
|
67
|
+
"lint:eslint": "cross-env NO_LOGS=true eslint --ext js,jsx,ts,tsx --max-warnings=0 --config .eslintrc.cjs",
|
|
68
68
|
"lint:eslint:fix": "pnpm run lint:eslint --fix",
|
|
69
69
|
"test": "vitest"
|
|
70
70
|
},
|