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

airborne-engine

v0.5.3

Published

Airborne RESTful API framework

Downloads

19

Readme

Airborne API framework

Moved to Airborne

This framework built for educational purpose. I'm migrating to ES6 and have decided to write my own RESTful API framework.

It is not covered by Unit tests yet but WIP.

How it works

It uses DAO architecture and DI for its carcass.

Using Express server routing it get all request and processes to Dispatcher. Dispatcher parses url into segments and apllies call to Controller's method.

Example:

GET /messages // MessagesController.load()
GET /messages/1 // MessagesController.get(id)
POST /messages // MessagesController.create(payload)

Also you can divide controllers by Modules. Engine will parse your url and process like this:

GET /todo/tasks // Todo/TasksController.load()

REQUEST params

They will arrive in method in params argument

GET /messages/1/?limit=100 // MessagesController.get(id, params)

Controllers

Engine will search for controllers in controllers folder or you can create modules. In that case you have to place in module folder. More about Controllers

App controllers

/app
  controllers
    IndexController.js

By module

/app
  modules
    Todo
      controllers
        TasksController.js

Config

You can provide your own config that will replace default

module.exports = {
  path: './',
  host: 'localhost', // API host to run
  port: 3000, // API port
  debug: true,

  // Database section
  // Available mappers: MySQL (MariaDB) / Redis / MongoDB
  db :{

    mysql: { // Name of the connection
      // Connection details in Databases section
    }
  }
}

Databases

MySQL

To enable MySQL support you need to provide in config connection information:

db: {
  ...
  mysql: { // Name of the connection
    host: '127.0.0.1',  // by default
    port: 3306,         // by default
    username: 'root',   // by default
    password: 'myPassword1', // by default - using password: NO
    database: 'MyDatabase' // no defaults
  }
}

Redis

db: {
  ...
  myRedis: { // Name of the connection
    host: '127.0.0.1',        // by default
    port: 6379,               // by default
    username: 'root',         // by default no user
    password: 'myPassword1'   // by default - using password: NO
  }
}

MongoDB

db: {
  ...
  myMongo: { // Name of the connection
    host: '127.0.0.1',        // by default
    port: 27017,              // by default
    username: 'root',         // by default no user
    password: 'myPassword1'   // by default - using password: NO
  }
}