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

sails-navigator

v0.7.6

Published

A route manager system that creates sails.js routes in a more manageable way

Downloads

31

Readme

sails-navigator

A route manager system that creates sails.js routes in a more manageable way

UNDER DEVELOPMENT - Any help is welcome

Examples

var navigator = require('navigator');

navigator(function(makeRoute){
  makeRoute('/')
    .GET('': 'HomeController.index');

  makeRoute('/news')
    .REST('!', 'index')
    /* Custom Routes */
    .GET('/follow': 'follow')
    .POST('/merge':  'merge')
    .GET('detach/:id': 'detach');
    
    /*
    * The previous call generates this RESTful routes
    * GET /news/new => NewsController.new
    * POST /news/new => NewsController.new // Used to postBack data on 301 redirect
    * GET /news/edit/:id => NewsController.edit
    * POST /news/edit/:id => NewsController.edit // Used to postBack data on 301 redirect
    * DELETE /news/:id => NewsController.destroy
    * POST /news => NewsController.create
    * PUT /news/:id => NewsController.update
    
    * And this custom routes
    * GET /news/follow => NewsController.follow
    * POST /news/merge => NewsController.merge
    * GET /detach/:id => NewsController.detach
    */

})    
var navigator = navigator = require('sails-navigator').config({
  pathToRecordFormat: '*/:id/:slug',
  localizeRoute: ['es', 'en'],
  defaultLocale: 'en',
  # LocalizedData should ideally go on an external file (It can be either JSON or a js object)
  localizedData: {
    '/': {en: '/', es:'/'}
    '/news': {en: '/news', es:'/noticias'}
  },
})

navigator(function(makeRoute){
  makeRoute('/')
    .GET('': 'HomeController.index');

  makeRoute('/news')
    .REST('index')
    
    /*
    * The previous call generates this RESTful routes
    * GET /news => NewsController.index
    * GET /news/new => NewsController.new
    * POST /news/new => NewsController.new
    * GET /news/edit/:id => NewsController.edit
    * POST /news/edit/:id => NewsController.edit
    * DELETE /news/:id => NewsController.destroy
    * POST /news => NewsController.create
    * PUT /news/:id => NewsController.update
    *
    * And the equivalent routes in spanish (Using localizedData)
    *
    * GET /es/noticias => NewsController.index
    * GET /es/noticias/nuevo => NewsController.new
    * POST /es/noticias/nuevo => NewsController.new
    * GET /es/noticias/editar/:id => NewsController.edit
    * POST /es/noticias/editar/:id => NewsController.edit
    * DELETE /es/noticias/:id => NewsController.destroy
    * POST /es/noticias => NewsController.create
    * PUT /es/noticias/:id => NewsController.update
    */

  makeRoute('/products')
    .confOverride({localizeRoute: ['en', 'es']})
    .REST('all');

})    

Note: makeRoute is a function passed as argument, to the function you provide to the navigator, so it can be called as you wish, but we'll stick to that naming convention.

API:

  • navigator.config Allows you to configure the settings for all routes, note that you can override this settings on a route basis using .confOverride. The options it accepts are the following:

  • pathToRecordFormat (String): This is used by the .REST method to build restful routes, by default it uses */:id to create routes like news/:id but could change it to something like this */:id/:slug to get news/:id/:slug

  • localizeRoute (Array|False): Specify which locales from the localizedData to use, i.e ['es', 'en']

  • defaultLocale (String): Used to determine how to guess the controllerName, so in a multilingual situation, you only want one controller name, not one for language, by default this option is set to en localizedData: (Object): If you are using localizedRoutes then you need to pass a translations object, where each key is the default language Path and it contains keys with translations for each language supported. e.g {'/news', {en: 'news', es: 'noticias'}}

  • makeRoute

    • .REST (String): It creates all restfull routes you specify, and it tries to guess the controller based on the passed route. It accepts the following options
      • 'All' It creates all restful routes index, show, edit, update and destroy
      • '*' An alias for 'All'
      • 'index', 'show' You can pass each route you want as a new argument
      • '!', 'update' If the first passed argument is a '!' it means, exclude the following routes

I'll try to update the documentation with more info anytime soon.