chore: lint

Author: pi0

.oxlintrc.json

@@ -3,6 +3,7 @@
   "plugins": ["unicorn", "typescript", "oxc"],
   "rules": {
     "no-unused-expressions": "off",
+    "no-unused-vars": ["warn", { "argsIgnorePattern": "^_" }],
     "typescript/unbound-method": "off",
     "typescript/no-floating-promises": "off",
     "typescript/no-implied-eval": "off",

src/rules/handlers/_utils.ts

@@ -158,9 +158,10 @@ function isLiterallyInScope(pathname: string, base: string): boolean {
  * 0 when it has no fixed count.
  *
  * Only a prefix whose every segment matches exactly one path segment can be
- * stripped by count. A catch-all or modifier param (`/:lang?/old`,
- * `/x/:seg*​/old`) matches a varying number, and so does a group spanning a
- * separator (`/x{/a}?/old`) — splitting it here leaves its braces unbalanced.
+ * stripped by count. A catch-all or modifier param (`/:lang?/old`, or a
+ * `:seg*` segment mid-prefix) matches a varying number, and so does a group
+ * spanning a separator (`/x{/a}?/old`) — splitting it here leaves its braces
+ * unbalanced.
  * Counting any of those strips the wrong number of segments off the request
  * path, so they return 0 and fall through to the literal comparison, which
  * rejects (400) instead of forwarding a silently mis-stripped path.

src/rules/match.ts

@@ -243,8 +243,8 @@ const OPAQUE_SEGMENT_RE = /[()\\]/;
 const CONCRETE_SEGMENT_RE = /^[^:*(){}\\]+$/;
 
 // A param that can match *zero* segments (`:x?`, `:x*`). rou3 reads such a
-// pattern as broader than the `**` that appears to absorb it (`/a/*​/:path*`
-// matches `/a/x`, which `/a/*​/**` does not), so it must never be absorbed.
+// pattern as broader than the `**` that appears to absorb it (`/a/*/:path*`
+// matches `/a/x`, which `/a/*/**` does not), so it must never be absorbed.
 const ZERO_MATCHABLE_SEGMENT_RE = /^:.*[?*]$/;
 
 /**

test/rules/compiler.test.ts

@@ -216,8 +216,8 @@ describe("generated code shape", () => {
   it("a compiled matcher with no override predicate still keeps a subsumed rule", () => {
     // The divergence this pins: `createMatcherFromFind`'s dependency-free default
     // predicate (`canOverrideRouteShape`) is not exact for modifier params — it
-    // cannot prove either direction between `/mod/reset/*​/**` and the
-    // `/mod/reset/*​/:path*` that actually subsumes it. Ordering matched layers
+    // cannot prove either direction between `/mod/reset/*/**` and the
+    // `/mod/reset/*/:path*` that actually subsumes it. Ordering matched layers
     // must therefore never consult a predicate, or the compiled default falls
     // back on arrival order and fails open: the broader pattern's `cors: false`
     // lands last and deletes the narrower rule. `evaluateCompiled` builds

test/rules/match.test.ts

@@ -144,7 +144,7 @@ describe("createMatcherFromFind override guard", () => {
     expect(canOverrideRouteShape("/admin/**", "/**")).toBe(false);
     expect(canOverrideRouteShape("/admin/**", "/public/**")).toBe(false);
     // …and the modifier-param shape fails closed in the direction rou3 orders
-    // it: `/a/*​/:path*` matches `/a/x`, which `/a/*​/**` does not, so the
+    // it: `/a/*/:path*` matches `/a/x`, which `/a/*/**` does not, so the
     // catch-all is the *narrower* pattern and must not absorb it.
     expect(canOverrideRouteShape("/a/*/**", "/a/*/:path*")).toBe(false);
     // …as does the optional-group shape, for the same reason one level down:

test/rules/merge.test.ts

@@ -27,7 +27,7 @@ describe("merge algorithm", () => {
   // pattern's, and its `false` reset deletes the narrower pattern's rule outright.
   // This is the default (no `preMerge`, no compiler) path.
   describe("matched layers are merged in containment order, not findAllRoutes order", () => {
-    // Two distinct upstream shapes: `/api/*​/:path*` subsumes `/api/*​/**` and comes
+    // Two distinct upstream shapes: `/api/*/:path*` subsumes `/api/*/**` and comes
     // back last in BOTH registration orders (rou3 sorts it there), while
     // `/admin/:page?` subsumes `/admin` and gets no specificity sort at all (both
     // weigh 0 in `pushSorted`, so config order survives) — hence both orders below.
@@ -627,7 +627,7 @@ describe("mergeMatchedRouteRules (pure)", () => {
     // Layer ordering must be decided by the build-time rank alone: the only
     // predicate a compiled matcher has by default is `canOverrideRouteShape`,
     // which is conservative but *not* exact for modifier params (it cannot see
-    // that `/api/*​/:path*` subsumes the `/api/*​/**` it appears to sit under, so
+    // that `/api/*/:path*` subsumes the `/api/*/**` it appears to sit under, so
     // it decides neither direction), leaving a predicate-driven order to fall
     // back on arrival order — which fails open exactly here. No `canOverride`
     // is passed below.