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

@qpjoy/electron-launcher-app-h2o

v2.3.0

Published

Home To Oversea embed network plugin for MX-H2I AppCenter.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

qpjoyqpjoy

Keywords

Readme

MX App H2O

@qpjoy/electron-launcher-app-h2o is H2O: Home To Oversea, the first MX-H2I AppCenter built-in embed network plugin. The product direction is a Clash-like user tool for proxy mode, PAC, Split DNS, rule status, and Internal access visibility, while the actual privileged network work remains owned by the MX-H2I standalone broker.

It is intentionally a normal npm-style Electron package: AppCenter can record the package name and version in Internal, cache the installed package locally, then open its entrypoint through the MX-H2I broker-session.

The default screen is user-facing: connection health, proxy mode, DNS/PAC status, and recent activity are visible without exposing launcher internals. Developers and support users can click Debug to inspect inherited MX-H2I context such as broker session, socket path, package metadata, network scope, local IP, and capability bridge state.

Development Test

From electron-dock/mx-launcher:

pnpm --filter @qpjoy/electron-launcher-app-h2o check
pnpm --filter @qpjoy/electron-launcher-app-h2o dev

The demo starts with a development broker registry so UI and broker-session states can be tested without a production socket. To verify the blocked embed path:

MX_H2O_BROKER_MODE=off pnpm --filter @qpjoy/electron-launcher-app-h2o dev

AppCenter Link

MX-H2I ships H2O in its default AppCenter catalog:

  • appId: h2o
  • packageName: @qpjoy/electron-launcher-app-h2o
  • launcherMode: embed
  • standaloneChannelProductId: mx-h2i
  • networkScope: broker-session
  • runtimeContractVersion: 0.1
  • requiredCapabilities: user.session, network.status, network.proxy, network.dns.policy, network.pac.policy, app-center-runtime
  • entrypoints.dev: workspace:demos/mx-app-h2o

In development, open MX-H2I, connect as guest or employee, install AppCenter, then install H2O from AppCenter. MX-H2I resolves entrypoints.dev to this workspace package, records the installed version and path in its local cache, and keeps operational details available from AppCenter's Debug button. Run this package with pnpm --filter @qpjoy/electron-launcher-app-h2o dev to test the embed UI directly.

In production, Internal admin should upsert the AppCenter record with the same package name and the release version. The client-side AppCenter cache stores installedVersion, latestVersion, installSource, entrypoints, install path, last action, and recent logs; the remote DB keeps the authoritative latest package/version and access policy.