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

dashex

v1.0.9

Published

Handling all the Express boilerplate with easy-outs.

Downloads

1

Readme

Handling all the Express boilerplate with easy-outs.

DashEX

npm monthly downloads github license

npm install dashex --save

(Thank you NPM!)

Purpose & Features

For (1) quickly spinning up alpha projects, (2) without worry about keeping your boilerplate simple, concise and consistent between projects, (3) full access to lower level dependencies, giving you 100% power and flexibility, (4) authentication strategies and view components to come.

Getting Started - Easy Start

var dashex = require('dashex')();

var app = dashex.app; //remember, js 'points' to the our dashex.app object, so we're not creating more overhead here

var express = dashex.express;

// view available objects, low-level dependencies and parameters
console.log(dashex);

Options - Intermediate / Advanced Start

var defaults = {
	configureInit: null, /* function override for setting initialization, including dotenv and connect-flash */
	configureParsers: null, /* function override for setting body parsers, including json */
	configurePublic: null, /* function override for setting static assets location */
	configureSessions: null, /* function override for enabling and configuring express-session */
	configureViews: null, /* function override for setting view engine and views location */
	dirname: '', /* __dirname of your application, so that any directories mount correctly from your application */
	port: 8080, /* in case no PORT is defined in process.env, express can at least start on this defined port */
	publicDir: 'public', /* instead of overriding public configuration, naming the directory for any public static assets */
	sessionInit: { /* instead of overriding session configuration, passing various options to modify express-sesssion behavior */
		secret: 'dash',
		resave: false,
		saveUninitialized: true
	},
	viewsDir: 'views', /* instead of overriding views configuration, naming the directory for any views to be rendered */
	viewEngine: 'pug' /* instead of overriding views configuration, setting our application's view engine */
};

var dashex = require('dashex')(options);

Public and Views Directories

By default, DashEX will create your public and views directories, for your static assets and template views respectively. If you want to bypass this behavior, simply pass empty strings to both publicDir and viewsDir options.

var defaults = {
	publicDir: ''
	viewsDir: ''
};

var dashex = require('dashex')(options);

Methods

dashex.run() instantiates express.listen for our application