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

core.io-express-server

v0.1.2

Published

core.io Express server module

Downloads

59

Readme

core.io-express

Express server module.

Config

  • port:
    • process.env.PORT
    • process.env.NODE_APP_PORT
    • 3000
  • basepath: Used to create the path to views and public.
  • locals: It will be made available to all requests through app.locals.
  • routeLocas: Specify locals per route. Example:
routeLocals: {
    '/admin': {
        layout: require('path').resolve('./modules/dashboard/views/layout.ejs')
    }
}

NOTE: Good idea to name all functions passed to app.use or router.use. Makes it easier to debug, which is true in general, since otherwise you would see <anonymous> as the output.

TODO

  • [ ] Handle unique assets, like favicon. config: { favicon: <ABSOLUTE_PATH>}
  • [ ] Provide a way to override layout for error.ejs
  • [ ] Default app: take config options
    • merge middleware
  • [ ] Asset pipeline:

Final Error Handler

For API calls:

res.send({
    success: false,
    message: error.message
});

Custom Error views

If our sub-app has the following view structure:

.
├── views
│   ├── error-layout.ejs
│   ├── 401.ejs
│   └── 403.ejs

The error view will be rendered with the following locals:

let locals = {
    isErrorView: true,
    status: status,
    message: err.message,
    error: err
};