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

mtcrawlee

v0.0.36

Published

爬虫程序,需要一个后台独立运行程序 之前的想法是 nextjs 的 api ,来提供 crawler worker 的数据和控制。但是,发现,nextjs 通常适合前端界面的数据渲染,而要做到对 worker 的实时控制之前的做法是: 使用消息队列。 但是发现,这个设计让整个系统之间的衔接变得复杂。

Downloads

9

Readme

用途

爬虫程序,需要一个后台独立运行程序 之前的想法是 nextjs 的 api ,来提供 crawler worker 的数据和控制。但是,发现,nextjs 通常适合前端界面的数据渲染,而要做到对 worker 的实时控制之前的做法是: 使用消息队列。 但是发现,这个设计让整个系统之间的衔接变得复杂。

现在考虑,使用点对点的方式(其中有一个中心服务点) 要点 1:搭配像 fly.io(256m 内存足够免费持续 运行一个 signal 服务)。 2: 后台可以基于 redis 等作为消息队列,不过,都隐藏在后台内部。而 worker 跟 server 之间的通信,使用 p2p 的方式。 3:前端可以做成纯静态页面(页面可以使用 p2p 的方式直接调用 server 服务,从而控制网内的 worker)

练习使用 libp2p