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

docset-generator

v0.3.0

Published

DocSet Generator

Downloads

129

Readme

DocSet Generator

Generates a docSet from html documentation.

Installation

npm install docset-generator --save

Usage

var DocSetGenerator = require('docset-generator').DocSetGenerator;
var docSetGenerator = new DocSetGenerator(
  {
    destination: "/path/to/dir",
    name: "MyDocSet",
    documentation: "/path/to/html"
  });
docSetGenerator.create();

Options

The DocSetGenerator constructor takes one parameter: new DocSetGenerator(configuration)

The configuration parameter is an object with the following keys.

  • name: name of the docSet
  • documentation: path to the html documentation
  • destination: path to the directory in which you want to generate the docSet [optional, falls back to the documentation folder]
  • enableJavascript: boolean, enable Javascript in the generated docSet
  • entries: Entries that will populate the docSet database [optional]
  • icon: path to the docSet icon [optional]
  • index: path to the index page of your html documentation [optional, default to index.html]
  • platformFamily: will be used to fill the DocSetPlatformFamily attribute in the Info.plist file [optional, falls back to the name]
  • identifier: will be used to fill the DocSetIdentifier attribute in the Info.plist file [optional, falls back to the name]

Entries

The entries parameter is an array of entries that will populate the sqlite3 database that comes with the docset.

Structure

Array<{ name:string, type:string, path:string }>

The type has to be one of the supported entry types.

This parameter is optional but without any entries, you won't get a neat overview of your documentation (list of classes, namespaces, methods and whatever else may be useful to you). You can use jsdoc-docset to generate those entries from inside your jsdoc template.