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

mtxrproxy

v0.1.235

Published

npm package template

Downloads

152

Readme

rproxy

反向代理

主要的第三方库

依赖的自定义库

  • mtx-graphql-server

设计备忘

  • 基本准则: 适当的将不同的功能分开到子项目。例如 mtx-graphql-server 因为痛苦的经理: - 之前,因为考虑docker, k8s,各种serverless云环境,所以弄了几十上百的project,最后都抛弃, 因为如果一套源码都想集中起来,会非常困难。难度成指数级增加,当到达一定数量后,人都蒙了。 可能弄了好几个月,到最后都弄不下去了。 现在发现,不管在什么环境,都只不过是npm i, npm run,而已。

      - 旧的开发方式,老是打算一个容器里面什么都做,不仅人受不了,机器也受不了。
        动不动一个project就好几个G的内存,cpu也经常100%。
        因为typescript,vscode 环境下有很多后台自动化功能。库太大了就卡死。
        如果还依赖python,甚至其他,就更加慢。慢得动都不动。
        如果分开不同的库,那么主项目使用的子项目都是已经编译好的代码, 性能直接飞起。

相关参考:

https://github.com/ljlm0402/typescript-express-starter.git