Bump flexsearch from 0.6.32 to 0.7.11

[dependabot]

Bumps flexsearch from 0.6.32 to 0.7.11.

Changelog

Sourced from flexsearch's changelog.

Changelog

v0.7.0

• Bidirectional Context (the order of words can now vary, does not increase memory when using bidirectional context)
• New memory-friendly strategy for indexes (switchable, saves up to 50% of memory for each index, slightly decrease performance)
• Better scoring calculation (one of the biggest concerns of the old implementation was that the order of arrays processed in the intersection has affected the order of relevance in the final result)
• Fix resolution (the resolution in the old implementation was not fully stretched through the whole range in some cases)
• Skip words (optionally, automatically skip words from the context chain which are too short)
• Hugely improves performance of long queries (up to 450x faster!) and also memory allocation (up to 250x less memory)
• New fast-update strategy (optionally, hugely improves performance of all updates and removals of indexed contents up to 2850x)
• Improved auto-balanced cache (keep and expire cache by popularity)
• Append contents to already existing entries (already indexed documents or contents)
• New method "contain" to check if an ID was already indexed
• Access documents directly from internal store (read/write)
• Suggestions are hugely improved, falls back from context search all the way down to single term match
• Document descriptor has now array support (optionally adds array entries via the new append under the hood to provide a unique relevance context for each entry)
• Document storage handler gets improved
• Results from document index now grouped by field (this is one of the few bigger breaking changes which needs migrations of your old code)
• Boolean search has a new concept (use in combination of the new result structure)
• Node.js Worker Threads
• Improved default latin encoders
• New parallelization model and workload distribution
• Improved Export/Import
• Tag Search
• Offset pagination
• Enhanced Field Search
• Improved sorting by relevance (score)
• Added Context Scoring (context index has its own resolution)
• Enhanced charset normalization
• Improved bundler (support for inline WebWorker)

Migration Quick Overview

The "async" options was removed, instead you can call each method in its async version, e.g. index.addAsync or index.searchAsync.

Define document fields as object keys is not longer supported due to the unification of all option payloads.

A full configuration example for a context-based index:

var index = new Index({
    tokenize: "strict",
    resolution: 9,
    minlength: 3,
    optimize: true,
    fastupdate: true,
    cache: 100,
    context: {
        depth: 1,
</tr></table> 

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)