chore: Only support next@14.2.0 and above

Author: franky47

.github/workflows/ci-cd.yml

@@ -23,15 +23,15 @@ jobs:
         # branch protection settings for `next`.
         base-path: [false, '/base']
         next-version:
-          - '13.4' # App router in GA
-          - '13.5'
-          - '14.0.1'
-          # 14.0.2 to 14.1.1 included are skipped as shallow routing
-          # implementation was experimental and unstable after GA release.
-          # 14.0.2 is not compatible due to a prefetch issue
-          # 14.0.3 is dropped due to a bug requiring WHS + syncing against uSP,
-          #        which creates other problems under other versions of Next.js
           - '14.1.2'
+          # - '14.1.3'
+          # - '14.1.4'
+          # - '14.2.0'
+          # - '14.2.1'
+          # - '14.2.2'
+          # - '14.2.3'
+          # - '14.2.4'
+          - '14.2.5'
           - latest
 
     steps:

packages/nuqs/package.json

@@ -56,8 +56,8 @@
     "prepack": "./scripts/prepack.sh"
   },
   "peerDependencies": {
-    "next": ">=13.4 <14.0.2 || >=14.1.2",
-    "react": "^18.2.0"
+    "next": ">= 14.1.2",
+    "react": ">= 18.2.0"
   },
   "dependencies": {
     "mitt": "^3.0.1"

packages/nuqs/src/update-queue.ts

@@ -186,16 +186,11 @@ function flushUpdateQueue(router: Router): [URLSearchParams, null | unknown] {
       // this allows keeping a reactive URL if the network is slow.
       const updateMethod =
         options.history === 'push' ? history.pushState : history.replaceState
-      // In 14.1.0, useSearchParams becomes reactive to shallow updates,
-      // but only if passing `null` as the history state.
-      // Older versions need to maintain the history state for push to work.
-      // This should theoretically be checking for >=14.0.5-canary.54 where WHS
-      // was stabilised, but we're not supporting canaries from previous GAs.
-      const state =
-        (window.next?.version ?? '') >= '14.1.0' ? null : history.state
       updateMethod.call(
         history,
-        state,
+        // In next@14.1.0, useSearchParams becomes reactive to shallow updates,
+        // but only if passing `null` as the history state.
+        null,
         // Our own updates have a marker to prevent syncing
         // when the URL changes (we've already sync'd them up
         // via `emitter.emit(key, newValue)` above, without