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

@nextop-os/workspace-file-manager

v0.0.16

Published

Reusable workspace file manager service, session state, host contracts, and optional React UI.

Readme

@nextop-os/workspace-file-manager

Reusable workspace file manager service, session state, host contracts, and optional React UI.

Hosts compose the package through createWorkspaceFileManagerService() and createSession(...). A session owns the shared file-manager data state, shared interaction state, preview flow, upload flow, and activation flow for one workspace-scoped instance.

Hosts provide backend capabilities through WorkspaceFileManagerHost. The package keeps shared state in logical workspace paths such as /workspace/src/index.ts and does not depend on nextopd, TSH, TACH, VM paths, or host absolute paths.

This package is intentionally a reusable frontend workspace-domain surface, not only a transport-agnostic data kernel. Shared session orchestration, preview flow, upload flow, activation flow, and React-facing interaction state may live here when they are part of the reusable file-manager experience across hosts.

The shared surface owns host-neutral file preview classification, activation-target shaping, shared view-model derivation, and the host contract needed to drive those flows so different hosts can integrate primarily by implementing WorkspaceFileManagerHost instead of rebuilding workflow around the shared UI.

Hosts now provide one app-level i18n runtime and scope it into the file-manager namespace, rather than hand-assembling package-local message objects.

What stays outside this package is concrete host integration: desktop preload calls, nextopd transport wiring, host absolute paths, and product-specific integration details belong in the owning host adapter.

Host Reuse Pattern

When another host wants to reuse this package:

  1. Implement WorkspaceFileManagerHost in the consuming host.
  2. Keep host transport, local-file picking, and environment-specific capabilities in that host adapter.
  3. Create one host-level i18n runtime that merges:
    • host-owned product i18n resources
    • workspaceFileManagerI18nResources
    • any other shared package i18n resources needed by the same surface
  4. Scope that runtime into the file-manager namespace with createWorkspaceFileManagerI18nRuntime(...).
  5. Override wording in the host runtime when the host intentionally owns the product phrasing; otherwise fall back to the package defaults.

This keeps the package reusable across different hosts without pushing host transport wiring or product wording into the shared package.