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 🙏

© 2026 – Pkg Stats / Ryan Hefner

param-links

v1.0.2

Published

Collection of parameter types and their reference links to use with documentation.js

Readme

param-links

Collection of parameter types with their respective reference links

This project is a helper meant to be used with Documentation.js.

As you may know, Documentation.js Node.js's API allows you to output the documentation result in different formats.

Each formatter accepts an options object, among which the path key is meant to link a parameter type with its respective source.

Let's say we want to generate our documentation in Markdown format.

And we want to document a simple Express route.

/**
 * Renders the welcome screen
 *
 * @name get/home
 * @memberof routes/app
 * @inner
 *
 * @param {Express.req}        req                      - Express request
 * @param {Express.res}        res                      - Express response
 * @param {Express.middleware} next                     - Express middleware
 *
 * @return {string} the rendered home template
 */
router.get('/', function (req, res, next) {
    res.render('index', {
        title: 'Welcome to my site'
    });
});

In that case, doing

	const paths = {
		"Express.req": 'http://expressjs.com/es/api.html#req',
  		"Express.middleware": 'http://expressjs.com/en/guide/using-middleware.html',
  		"Express.res": 'http://expressjs.com/es/api.html#res'
	};

	documentation.build(['routes/app.js'])
	.then(res => {
    	return documentation.formats.md(res, { 	paths    });
	}).then(output => {
    
    	return fs.writeFileSync(`${__dirname}/ROUTE.md`, output);

	}).catch(function (err) {
	    console.error(err);
	    return;
	});
  

Will automagically link those Express-type parameters to their respective docs and definitions.

Documentation.js already does this for native JS primitives (strings, numbers, objects, arrays...) pointing to MDN, but you can expand that feature as far as you want.

At this point, there are parameters for

  • Google Maps API
  • GeoJSON Types
  • Backbone objects
  • Express objects
  • Facebook API endpoints and types

So instead of manually writing your parameter-link mapping, you can do:


	let paths = require('param-links');
	
	// add or replace paths as you wish
	Object.assign(paths, {
		paramx:'https://paramx.com'
	});

	documentation.build(...)

Let me see those contributions!