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

mserver

v0.0.0

Published

A simple web application framework for Node.

Downloads

31

Readme

Feel free to change or remove this file, it is informational only.

Repo layout

node_modules/ - Any Node modules packaged with the app deplist.txt - Deprecated. package.json - npm package descriptor. .openshift/ - Location for openshift specific files .openshift/action_hooks/pre_build - Script that gets run every git push before the build .openshift/action_hooks/build - Script that gets run every git push as part of the build process (on the CI system if available) .openshift/action_hooks/deploy - Script that gets run every git push after build but before the app is restarted .openshift/action_hooks/post_deploy - Script that gets run every git push after the app is restarted

Notes about layout

Please leave the node_modules and .openshift directories but feel free to create additional directories if needed.

Note: Every time you push, everything in your remote repo dir gets recreated please store long term items (like an sqlite database) in the OpenShift data directory, which will persist between pushes of your repo. The OpenShift data directory is accessible relative to the remote repo directory (../data) or via an environment variable OPENSHIFT_DATA_DIR.

Environment Variables

OpenShift provides several environment variables to reference for ease of use. The following list are some common variables but far from exhaustive: process.env.OPENSHIFT_GEAR_NAME - Application name process.env.OPENSHIFT_GEAR_DIR - Application dir process.env.OPENSHIFT_DATA_DIR - For persistent storage (between pushes) process.env.OPENSHIFT_TMP_DIR - Temp storage (unmodified files deleted after 10 days)

When embedding a database using 'rhc app cartridge add', you can reference environment variables for username, host and password: process.env.OPENSHIFT_DB_HOST - DB Host process.env.OPENSHIFT_DB_PORT - DB Port process.env.OPENSHIFT_DB_USERNAME - DB Username process.env.OPENSHIFT_DB_PASSWORD - DB Password

When embedding a NoSQL database using 'rhc app cartridge add', you can reference environment variables for username, host and password: process.env.OPENSHIFT_NOSQL_DB_HOST - NoSQL DB Host process.env.OPENSHIFT_NOSQL_DB_PORT - NoSQL DB Port process.env.OPENSHIFT_NOSQL_DB_USERNAME - NoSQL DB Username process.env.OPENSHIFT_NOSQL_DB_PASSWORD - NoSQL DB Password

To get a full list of environment variables, simply add a line in your .openshift/action_hooks/build script that says "export" and push.

deplist.txt

A list of node modules to install, line by line on the server. This will happen when the user does a git push.

Additional information

Link to additional information will be here, when we have it :)