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

@wfh/assets-processer

v1.2.0-2

Published

Work with Plink, copy assets to destDir folder only when devMode is false

Downloads

2

Readme

Utilities

Functions

| utils.ts functions | Description |- |- | createResponseTimestamp() | Middleware for printing each response process duration time to log | commandProxy() | Create an HTTP request proxy middleware and use for specific request path

Deploy and file server runtime

Use case

A cheap version of Static Content update mechnism, in which case we don't need involve any Redis like cross machine/cluster cache/storage service.

Pros: No polling required. Cons: To make sure all (both) nodes are reached and updated, must try multiple times.

graph LR
buildBox((build<br>machine))
env((Runtime<br>env))

subgraph assets-processer tool
   fetchOtherZip(Fetch other<br>zip files)
   sendZip(upload<br>to all nodes<br>master<br>process)
   upload[Repeat uploading,<br>until all<br>nodes are<br>updated]
   storeZip[stored zip]
end

subgraph assets-processer runtime
   rejDupli(Accept connection,<br>verify if it is<br>duplicate<br>uploading)
   unzip(extract<br>zip files<br>and delete)
end

buildBox --> staticBuild(build<br>static only)
staticBuild -.-> |1. include| build(compile)
build ---|output| zip[zip<br>file]
staticBuild -.-> |2. include| sendZip

buildBox --> fullBuild(Full build)

fullBuild -.->|1.| build
fullBuild -.->|2.| fetchOtherZip
fullBuild -.-> |3. include| sendZip
sendZip -.->|include| upload
sendZip --> |store|storeZip
fetchOtherZip --> |get|storeZip

sendZip -.-> |include| rejDupli
rejDupli ---|store & compare| version[app name,<br>version]
rejDupli -.->|include|unzip

fullBuild -.->|5.| gitCommit(git<br>commit/push/tag<br>release/*)
fullBuild -.-> |0.| buildNode(build Node<br>side *.ts)

env --> deploy(being<br>deployed)
env --> reboot(reboot on<br>fail over)


deploy -.-> |include| unzip
admin((admin)) --> mailNotif(Can recieve mail:<br>current<br>app zip<br>names/version)
admin --> seeVersion(query version<br>and node id)
mailNotif --> version
seeVersion --> version