fix(match): explicitly reject useTokenSearch in Fuse.match

Token search needs corpus statistics (df, fieldCount) that a one-off
string comparison can't provide. Behavior used to diverge by build:

- Full build: TokenSearch destructured `options._invertedIndex` and
  crashed with an opaque TypeError.
- Basic build: TokenSearch isn't registered, so createSearcher silently
  fell back to BitapSearch and returned a normal fuzzy match — quietly
  divergent from the full build.

Guard `useTokenSearch` directly in Fuse.match before calling
createSearcher, so both builds throw the same explicit error.

Plan 007.

Author: krisk

README.md

@@ -174,6 +174,8 @@ const result = Fuse.match('javscript', 'JavaScript: The Good Parts')
 // → { isMatch: true, score: 0.04, indices: [[0, 9]] }
 ```
 
+`Fuse.match()` does **not** support `useTokenSearch` — token search requires corpus-level statistics (`df`, `fieldCount`) that a one-off string comparison can't provide. Passing `useTokenSearch: true` throws an explicit error. Use `new Fuse(docs, { useTokenSearch: true }).search(query)` for token-search behavior.
+
 ### Dynamic Collections
 
 Add and remove documents from a live index without rebuilding.

src/entry.ts

@@ -5,13 +5,22 @@ import { parse } from './core/queryParser'
 import { ExtendedSearch } from './search'
 import TokenSearch from './search/token'
 import register, { createSearcher } from './core/register'
+import * as ErrorMsg from './core/errorMessages'
 
 Fuse.version = '__VERSION__'
 Fuse.createIndex = createIndex
 Fuse.parseIndex = parseIndex
 Fuse.config = Config
 
 Fuse.match = function (pattern: string, text: string, options?: any) {
+  // Token search needs corpus statistics (df, fieldCount) that a one-off
+  // string comparison can't provide. Reject it here so the contract is the
+  // same in the full and basic builds — without this guard, the full build
+  // crashes with an opaque TypeError and the basic build silently falls back
+  // to fuzzy matching.
+  if (options && options.useTokenSearch) {
+    throw new Error(ErrorMsg.FUSE_MATCH_TOKEN_SEARCH_UNSUPPORTED)
+  }
   const searcher = createSearcher(pattern, { ...Config, ...options })
   return searcher.searchIn(text)
 }

test/match.test.js

@@ -1,4 +1,6 @@
 import Fuse from '../dist/fuse.mjs'
+import FuseBasic from '../dist/fuse.basic.mjs'
+import * as ErrorMsg from '../src/core/errorMessages'
 
 describe('Fuse.match', () => {
   test('returns a match for a fuzzy match', () => {
@@ -59,4 +61,25 @@ describe('Fuse.match', () => {
       expect(end - start + 1).toBeGreaterThanOrEqual(3)
     })
   })
+
+  // Token search needs corpus-level statistics (df, fieldCount) that a one-off
+  // string comparison can't provide. Both builds must reject it explicitly —
+  // the full build used to crash with an opaque TypeError, the basic build
+  // used to silently fall back to plain fuzzy matching.
+  test('throws when useTokenSearch is true (full build)', () => {
+    expect(() =>
+      Fuse.match('apple', 'apple pie', { useTokenSearch: true })
+    ).toThrowError(ErrorMsg.FUSE_MATCH_TOKEN_SEARCH_UNSUPPORTED)
+  })
+
+  test('throws when useTokenSearch is true (basic build)', () => {
+    expect(() =>
+      FuseBasic.match('apple', 'apple pie', { useTokenSearch: true })
+    ).toThrowError(ErrorMsg.FUSE_MATCH_TOKEN_SEARCH_UNSUPPORTED)
+  })
+
+  test('still works when useTokenSearch is explicitly false', () => {
+    const result = Fuse.match('apple', 'apple pie', { useTokenSearch: false })
+    expect(result.isMatch).toBe(true)
+  })
 })