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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@lingxiteam/engine-businesscomponent

v4.1.1-alpha.10

Published

## 网络日志记录 debugPrinter.networklog/debugPrinter.networkfinish

Downloads

221

Readme

日志管理库内置的共享topic(事件)如下,请其他模块按此要求调用:

网络日志记录 debugPrinter.networklog/debugPrinter.networkfinish

开始时间/结束时间会由plog库内置按照networklog或networkfinish自行处理

// 请求发起时
LogManager.trigger('debugPrinter.networklog', {
    reqSeq, // 请求的标识,必传,当触发networkfinish时需要以此来寻找对应请求,请求标识不限格式,也可以是某个自增序列,但需要保证唯一
    url, // 网络请求地址
    options, // 本次请求的fetch设置对象,包括method、header、param这些东西,供网络工具二次处理
    cmddata: { // 如果本次网络请求是由指令发起,可以传入额外的信息(用于定位是哪条指令),非必传
        cmd, // 本条指令记录对象
        appId, // 这些ID用于定位是哪个页面
        pageId,
        busiCompId,
    }
});

// 请求完成时
LogManager.trigger('debugPrinter.networkfinish', {
    reqSeq, // 请求的标识,必传,以对应发起时的请求 
    resultData,// 请求结果的数据,
    resultCode,// 请求结果状态,'success'或'error',
});

指令系统输出错误信息 cmdplayer.errorMsg

通用。指令系统本身输出的错误信息会统一抛出该事件。具体页面运行态监听这个事件来决定是弹出错误信息弹窗还是什么

LogManager.trigger('cmdplayer.errorMsg', { ...errorOptions });