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

icepop

v1.1.0

Published

Quickly bootstrap a Express+Mongoose API

Downloads

5

Readme

Icepop

Quickly bootstrap a Express+Mongoose API :warning: This is a V1, the code isn't very dry & it might not suit your project at the moment.

Installation

$ npm install icepop

Get started

This guide is designed for an Express + Mongoose server, eg:

const express = require('express');
const app = express();

const mongoose = require('mongoose');

mongoose.Promise = global.Promise;
mongoose.connect('localhost:27017/icepop_example');

mongoose.connection.on('open', () => {
  console.info('Mongoose connection open');
});

app.listen(5000, function () {
  console.info(`Icepop test server listening on port 5000`);
});

To setup your API routes, simply require icepop & give it your API definitions (Covered below)

const icepop = require('icepop');
const spec = {}; // Explained below...
app.use('/api', icepop(spec));

Definitions spec

{
  versions: {
    'v1': { // Scope out your different schema versions easily
      entities: [
        {
          id: 'cat', // This should be the unique name of your entity.
          getBy: ['_id', 'name'], // These are properties you can use to individually get this entity. eg: GET /api/v1/cat/_id/123456789
          queryBy: ['_id', 'name', 'owner'], // These are properties you can use to query by & paginate on. eg: GET /api/v1/cat?_owner=bob&page=2
          createFields: ['name', 'owner'], // These are properties that must be filled out when creating a new entity via POST
          edit: {
            by: ['_id'], // These are the fields you can query by for an edit. eg: PUT /api/v1/cat/_id/123456789
            fields: ['name', 'owner'], // These are fields you can actually change
          },
          deleteBy: ['_id'], // These are the fields you can query for for a delete. eg: DELETE /api/v1/cat/_id/123456789
          populate: { // These are fields that have embedded mongo documents and should be populated when queried
            path: 'owner', // Path of the population field
            model: 'Person', // Type of model being populated
          },
          model: Cat, // The Mongoose object
          deprecated: true, // Indicate this model for this api scope is deprecated
        }
      ]
    },
  },
  security: {
    key: 'abcdefg123456', // Set a API secret key. eg: process.env.API_KEY
  },
}

Generated API Documentation

Api Docs are automatically generated for your API spec. Visit /api/docs in your application. (Soon).

Local dev

git clone npm install

For testing changes, use npm run server to start a dev server, and npm run test to execute all tests. (You'll need Mongo running to execute both).

TESTS TO WRITE

  • multiple versions
  • deprecation notice
  • population

TODO

  • enforce lowercase, no space ID