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/express-app

v1.1.11

Published

Work with Plink, base Express app

Downloads

5

Readme

Express server

This package contains Express web framework as core package. Also this package is API provider.

Supported Express middlewares

You don't need to add following middleware, they have already been onboard.

  • cookie-parser

  • body-parser

  • compression

new API

New Node API methods | Name | description |-- | -- | .router() | return an Express Router object | .use() | Express use() method, to bind middleware | .param() | Express param() method | .expressAppSet(callback) | callback: function(app, express), whatever things you want to do before express's app getting initialized | .swig | express view engines: require('swig-template') | .express | express instance, so that you can access some express middleware, like api.express.static | .expressApp | the main express app instance used by us, which is value of express() | .cors() | CORS middleware for specific route path, e.g. api.router().use('/api', api.cors()); check setupApi.js

Above API methods must be called within module.exports.activate() function e.g.

var api = require('__api');

exports.activate = function() {
	api.router().get(function(req, res) {
		res.render('/template.html');
	});
};

e.g. expressAppSet(callback)

exports.activate = function(){
 	api.expressAppSet((app, express) => {
 		app.set('trust proxy', true);
		app.set('views', Path.resolve(__dirname, 'web/views/'));
	});
};

Check server side git hash

You need put generate a git hash text file in root folder like,

git rev-parse HEAD > githash-server.txt
echo \"I am in Dev\" >> githash-server.txt

Or put in your package.json npm script:

"scripts": {
	"build": "git rev-parse HEAD > githash-server.txt && echo \"I am in Dev\" >> githash-server.txt:
}

Once your start server by node app, you can access /githash-server or /githash-server.txt