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

@mnpjs/idio

v1.3.1

Published

The Idio Web Server MNP Structure For Easy Node.js Backend Website Building.

Downloads

12

Readme

@mnpjs/idio

The Idio Web Server MNP Structure For Easy Node.js Backend Website Building.

import core from '@idio/core'
import facebook from '@idio/facebook'

(async () => {
  const { app, router, url } = await core({
    session: { use: true,
      keys: [process.env.SESSION_KEY || 'dev'],
    },
    logger: { use: process.env != 'production' },
    static: { use: true, root: 'static' },

  }, { port: process.env.PORT || 5000 })
  router.get('/', async (ctx, next) => {
    ctx.body = 'hello world'
    await next()
  })
  facebook(router, {
    client_id: process.env.CLIENT_ID,
    client_secret: process.env.SECRET,
  })
  app.use(router.routes())
  console.log('Started on %s', url)
})()

Structure

The project will have the minimal structure to start the webserver.

structure
├── CHANGELOG.md
├── Dockerfile
├── README.md
├── build
│   └── bin
│       └── app.js
├── documentary
│   ├── 1-dokku.md
│   ├── 2-facebook.md
│   ├── 3-env.md
│   ├── footer.md
│   └── index.md
├── package.json
├── src
│   └── bin
│       ├── app.js
│       └── index.js
├── static
└── yarn.lock

Using With MNP

This structure is cloned with appropriate parameters (i.e., copyright links and license placeholders) using the mnp package bootstrapper.

mnp new-website -s idio

Dockerfile

The webserver is meant to be deployed on a docker conatiner (e.g., on a Dokku host is optimal). The following Dockerfile based off node:alpine is used.

FROM node:10-alpine

COPY package*.json .
COPY yarn.lock .
RUN yarn

COPY build build
COPY static static

ENV NODE_ENV production

ENTRYPOINT ["node", "build/bin/app.js"]

Copyright

(c) Art Deco 2018