next-rest-framework
Advanced tools
Comparing version
@@ -34,3 +34,3 @@ #!/usr/bin/env node | ||
name: "next-rest-framework", | ||
version: "5.1.8", | ||
version: "5.1.9", | ||
description: "Next REST Framework - Type-safe, self-documenting APIs for Next.js", | ||
@@ -77,3 +77,4 @@ keywords: [ | ||
"tiny-glob": "0.2.9", | ||
"zod-to-json-schema": "3.21.4" | ||
"zod-to-json-schema": "3.21.4", | ||
qs: "6.11.2" | ||
}, | ||
@@ -83,2 +84,3 @@ devDependencies: { | ||
"@types/lodash": "4.14.197", | ||
"@types/qs": "6.9.11", | ||
jest: "29.6.4", | ||
@@ -85,0 +87,0 @@ "node-mocks-http": "1.13.0", |
@@ -28,3 +28,3 @@ "use strict"; | ||
name: "next-rest-framework", | ||
version: "5.1.8", | ||
version: "5.1.9", | ||
description: "Next REST Framework - Type-safe, self-documenting APIs for Next.js", | ||
@@ -71,3 +71,4 @@ keywords: [ | ||
"tiny-glob": "0.2.9", | ||
"zod-to-json-schema": "3.21.4" | ||
"zod-to-json-schema": "3.21.4", | ||
qs: "6.11.2" | ||
}, | ||
@@ -77,2 +78,3 @@ devDependencies: { | ||
"@types/lodash": "4.14.197", | ||
"@types/qs": "6.9.11", | ||
jest: "29.6.4", | ||
@@ -79,0 +81,0 @@ "node-mocks-http": "1.13.0", |
{ | ||
"name": "next-rest-framework", | ||
"version": "5.1.8", | ||
"version": "5.1.9", | ||
"description": "Next REST Framework - Type-safe, self-documenting APIs for Next.js", | ||
@@ -39,3 +39,4 @@ "keywords": [ | ||
"tiny-glob": "0.2.9", | ||
"zod-to-json-schema": "3.21.4" | ||
"zod-to-json-schema": "3.21.4", | ||
"qs": "6.11.2" | ||
}, | ||
@@ -45,2 +46,3 @@ "devDependencies": { | ||
"@types/lodash": "4.14.197", | ||
"@types/qs": "6.9.11", | ||
"jest": "29.6.4", | ||
@@ -47,0 +49,0 @@ "node-mocks-http": "1.13.0", |
@@ -126,8 +126,2 @@ <p align="center"> | ||
When using the default `nodejs` runtime, you may encounter the [Dynamic server usage](https://nextjs.org/docs/messages/dynamic-server-error) Next.js error when running `next build`. In that case you should force the route to be dynamically rendered with the [dynamic](https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#dynamic) option: | ||
```typescript | ||
export const dynamic = 'force-dynamic'; | ||
``` | ||
#### [Pages router docs API route](#pages-router-docs-api-route): | ||
@@ -248,2 +242,8 @@ | ||
When using the default `nodejs` runtime with app router routes (`docsRoute` or `route`), you may encounter the [Dynamic server usage](https://nextjs.org/docs/messages/dynamic-server-error) Next.js error when running `next build`. In that case you should force the route to be dynamically rendered with the [dynamic](https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#dynamic) option: | ||
```typescript | ||
export const dynamic = 'force-dynamic'; | ||
``` | ||
##### [Pages router API route](#pages-router-api-route): | ||
@@ -250,0 +250,0 @@ |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is too big to display
Sorry, the diff of this file is not supported yet
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
1443106
36.85%110
32.53%42939
44.98%8
14.29%12
9.09%+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added
+ Added