[Snyk] Upgrade flexsearch from 0.7.43 to 0.8.105

[nerdy-tech-com-gitub]

Snyk has created this PR to upgrade flexsearch from 0.7.43 to 0.8.105.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 4 versions ahead of your current version.

• The recommended version was released 21 days ago.

Release notes

Package name: flexsearch

• 0.8.105 - 2025-03-19
• 0.8.103 - 2025-03-17
• 0.8.1 - 2025-03-17
  
  • Resolver Support for Documents
  • Asynchronous Runtime Balancer, new option priority
  • Export/Import Worker Indexes + Document Worker, new extern config options export and import
  • Improved interoperability of the different build packages, including source folder
  • Support custom filter function for encoder (stop-word filter)
• 0.8.0 - 2025-03-17
  
  • Persistent indexes support for: IndexedDB (Browser), Redis, SQLite, Postgres, MongoDB, Clickhouse
  • Enhanced language customization via the new Encoder class
  • Result Highlighting
  • Query performance achieve results up to 4.5 times faster compared to the previous generation v0.7.x by also improving the quality of results
  • Enhanced support for larger indexes or larger result sets
  • Improved offset and limit processing achieve up to 100 times faster traversal performance through large datasets
  • Support for larger In-Memory index with extended key size (the defaults maximum keystore limit is: 2^24)
  • Greatly enhanced performance of the whole text encoding pipeline
  • Improved indexing of numeric content (Triplets)
  • Intermediate result sets and Resolver
  • Basic Resolver: and, or, xor, not, limit, offset, boost, resolve
  • Improved charset collection
  • New charset preset soundex which further reduces memory consumption by also increasing "fuzziness"
  • Performance gain when polling tasks to the index by using "Event-Loop-Caches"
  • Up to 100 times faster deletion/replacement when not using the additional "fastupdate" register
  • Regex Pre-Compilation (transforms hundreds of regex rules into just a few)
  • Extended support for multiple tags (DocumentIndex)
  • Custom Fields ("Virtual Fields")
  • Custom Filter
  • Custom Score Function
  • Added French language preset (stop-word filter, stemmer)
  • Enhanced Worker Support
  • Export / Import index in chunks
  • Improved Build System + Bundler (Supported: CommonJS, ESM, Global Namespace), also the import of language packs are now supported for Node.js
  • Full covering index.d.ts type definitions
  • Fast-Boot Serialization optimized for Server-Side-Rendering (PHP, Python, Ruby, Rust, Java, Go, Node.js, ...)
• 0.7.43 - 2024-01-10

from flexsearch GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Enhancements:

• Upgrade brings significant performance improvements and new features to the flexsearch library

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request upgrades the flexsearch dependency from version 0.7.43 to 0.8.105 in package.json.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
The pull request upgrades the flexsearch dependency.	Upgraded flexsearch from version 0.7.43 to 0.8.105.	docs/docs.trychroma.com/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.