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

@loopstack/remote-file-explorer-example-workflow

v0.22.0

Published

Example workflow demonstrating @loopstack/remote-file-explorer-module — lists a remote workspace tree and reads a file

Readme

@loopstack/remote-file-explorer-example-workflow

Demonstrates browsing a remote workspace. Imports @loopstack/remote-file-explorer-module so its HTTP endpoints (GET /tree, GET /read) are live, and ships a small workflow that mirrors the same flow using GlobTool + ReadTool from @loopstack/remote-client.

By using this example you'll get...

  • The RemoteFileExplorerController mounted at /api/v1/workspaces/:workspaceId/files/*
  • A RemoteFileExplorerExampleWorkflow that lists files and reads one from the remote agent
  • A reference wiring for frontends that want to render a remote file tree

Installation

loopstack add @loopstack/remote-file-explorer-example-workflow

@loopstack/remote-client must be configured with a sandbox environment pointing at a running remote agent.

How It Works

  1. The workflow globs **/*.md from the workspace root using GlobTool.
  2. It reads the first match using ReadTool.
  3. Both results are saved as MessageDocuments.
  4. Separately, the RemoteFileExplorerController mounted by the module exposes the same primitives as HTTP endpoints the frontend can hit directly.

Public API

  • RemoteFileExplorerExampleModule
  • RemoteFileExplorerExampleWorkflow

Dependencies

  • @loopstack/common, @loopstack/core
  • @loopstack/remote-client
  • @loopstack/remote-file-explorer-module