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

interface-log

v1.1.8

Published

A lightweight front-end debugging tool used to debug the mobile client interface (jsbridge).

Readme

English | 简体中文

interface-log

A lightweight front-end debugging tool used to debug the mobile client interface (jsbridge).

When developing some h5 pages embedded in webview, some capabilities provided by the client are used, or some data needs to be obtained from the client. This method is mostly the jsbridge method. The principle is to call the client-side function registered under a certain attribute of the global object window, and get the data from the function return value or the corresponding callback. This kind of data cannot be viewed through Chrome://inspect, and Charles cannot capture packets (maybe I don't know). Interface-log records the calling process of jsbridge function in a visual way, and returns data to improve the efficiency of development and testing.

how to use

npm

interface-log must be initialized before the client interface is called

  • Import interface-log to initialize instance objects in the form of constructor
  • Pass in the bridge name of jsbridge (The global object name used by the client to mount the function)
npm i interface-log
yarn add interface-log
import InterfaceLog from 'interface-log';
new InterfaceLog({bridge:['bridgeName']});

cdn

<script src="https://unpkg.com/interface-log@latest"></script>
<!-- @latest can be specific version,like @1.1.2 -->

Referring unpkg

tips

  1. Click the replay icon next to name to execute the request again.

  2. The execution stage is distinguished by taking a snapshot of the function execution state, including four states of ready, processing, sync-finish, and async-finish, and the call state is distinguished by color.

    • The ready function has been initialized and is ready to be called.
    • The processing function is being executed.
    • sync-finish synchronization function execution ends.
    • async-finish asynchronous function (getting the return value through callback) function execution ends.
  3. Long press on the list content item to display the content details.

  4. Slide a single record to the right to delete it.

Referring vconsole implementation

License

MIT