npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sirasagi62/flf

v0.1.1

Published

A command-line tool for semantically exploring code.

Readme

Fluent Finder (Flf)

Fluent Finder (Flf) is a vector-based code search tool with a fuzzy-finder-like interactive UI. It enables fast, semantic search across your codebase by combining code parsing, embedding generation, and similarity search.

Flf supports two primary modes:

  • dir: Search through all code files in a directory.
  • buf: Search through the current buffers of your text editor (requires external buffer export).

It integrates seamlessly with Neovim, Vim or outputs plain JSON for custom scripting. You can use flf-vim for Vim/Neovim integration.


🚀 Installation

Due to the bug in Bun that can prevent proper operation, please install using Node.js with npm or pnpm instead.

Using pnpm

npm install -g @sirasagi62/flf
pnpm add -g @sirasagi62/flf

Flf uses @huggingface/transformers and veqlite under the hood for embedding generation and vector search.


📁 Directory Search (dir)

Search through all code files in a given directory.

Basic Usage

flf dir -p /path/to/your/project
  • -p or --path: Path to the directory to search (defaults to .).
  • -e or --editor: Output format (nvim, vim, cmd). Default: cmd.

Example: Open result in Neovim

flf dir -p . -e nvim

When you select an item, it outputs a Neovim command like:

<cmd>tabf +10 ./src/index.ts<CR>

That sends via nvim remote functions and it works with flf-vim


💾 Buffer Search (buf)

Search through the current buffers of your text editor. This mode requires you to export your editor's buffer content as JSON first.

Step 1: Export Editor Buffers

Create a JSON file containing your current buffers. The format should be:

[
  {
    "buffername": "/full/path/to/file1.ts",
    "content": "function hello() {\n  console.log('Hello');\n}"
  },
  {
    "buffername": "/full/path/to/file2.py",
    "content": "def greet():\n    print('Hi')\n"
  }
]

How to export: Use your editor's API to list open buffers and their content. For Neovim, you can use flf-vim.

Step 2: Run Flf on Buffer Data

flf buf -p /path/to/buffers.json
  • -p or --path: Path to the JSON file containing buffer data.
  • -e or --editor: Output format (same as dir).

🖥️ Interactive UI

Flf launches an interactive TUI powered by blessed:

  • Input box: Type your search query.
  • Left panel: Shows matching code entities (functions, classes, etc.).
  • Right panel: Syntax-highlighted preview of the selected item.

Keybindings

  • / : Navigate results.
  • Enter: Select and output result.
  • Backspace: Edit query.
  • Esc / q / Ctrl+C: Quit.

🧩 Output Formats (-e)

| Format | Output Example | |--------|----------------| | nvim | <cmd>tabf +10 ./src/index.ts<CR> | | vim | <cmd>tabf +10 ./src/index.ts<CR> | | emacs| (Planned) | | cmd | Raw JSON output |

For Neovim/Vim, you can use flf-vim for high level integration.


🛠️ How It Works

  1. Parsing: Uses code-chopper to parse code into functions, classes, etc.
  2. Embedding: Generates vector embeddings using a Hugging Face ONNX model.
  3. Indexing: Stores chunks in a vector database (veqlite with PGLite).
  4. Search: Performs similarity search on user query.

All processing is done locally — no data leaves your machine.


📂 Project Structure

  • src/index.ts: CLI entrypoint with yargs.
  • src/dircore.ts: Core logic for directory indexing.
  • src/buffercore.ts: Core logic for buffer indexing.
  • src/buffer-loader.ts: Loads buffer JSON.
  • src/types.ts: Shared types.

📷 Screenshots

Coming soon


📄 License

MIT