vpndetection-next 2.1.2 → 2.1.3

package/README.md

@@ -43,15 +43,28 @@ Then read the answer anywhere downstream:
 
 ```tsx
 // app/page.tsx
+import { Suspense } from 'react';
 import { headers } from 'next/headers';
 import { readLookup } from 'vpndetection-next';
 
-export default async function Page() {
+async function Greeting() {
     const lookup = readLookup(await headers());
-    return <main>{lookup?.isVpn ? 'Hello, VPN user' : 'Hello'}</main>;
+    return lookup?.isVpn ? 'Hello, VPN user' : 'Hello';
+}
+
+export default function Page() {
+    return (
+        <main>
+            <Suspense fallback="Hello">
+                <Greeting />
+            </Suspense>
+        </main>
+    );
 }
 ```
 
+The read of `headers()` sits inside `<Suspense>` because a new Next 16 app turns Cache Components on, and `next build` then refuses a page that reads request data outside one.
+
 By default nothing is blocked. Your own code decides what the answer means — which is usually what you want, because whether a VPN visitor is a problem depends entirely on what they are doing.
 
 **Set a `matcher`.** Without one the proxy runs on every request including static assets, which costs a lookup each.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vpndetection-next",
-  "version": "2.1.2",
+  "version": "2.1.3",
   "description": "Official Next.js proxy/middleware for the VPNDetection API. Detect VPNs, proxies, Tor, hosting and CDN visitors on every request.",
   "type": "module",
   "license": "MIT",
@@ -44,7 +44,7 @@
     "node": ">=22"
   },
   "dependencies": {
-    "vpndetection": "^5.5.3"
+    "vpndetection": "^5.6.0"
   },
   "peerDependencies": {
     "next": ">=15"