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 🙏

© 2025 – Pkg Stats / Ryan Hefner

simpler_process

v0.0.6

Published

directories 0.0.4 is controlled with this following variable: vda

Readme

this is the ground floor(foundation) of simpler process

var vda;
vda = {
'env':{
 'PORT':'',
 'IP':'',
 'PATH':{
   'main':'./server.js',
   'sub':'./README.md',
   'package':'./package.json',
   'secrets':'./env'
},
},
'process':process.env,
}

you must have a main called server.js, a sub README.md, your package.json, and your .env the reason why they are so close, is because it acts like a shell variable, if you want to add more directories(PATH), use the following information provided:

'<call>':'./<filename>.<script type>',

the way to add a different area is by going to 2 above the last bracket, and put in some type of variable IN ALL CAPITALS(this will come in handy in later updates), then put some sub info in brackets after the : to add on a main system do the following go 1 up from the bottom bracket and do the following:

'<sub>':{
'<info>':'<info>',
}

there are constant updates to this package, ending with 10.99.42.4