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

@buildium/angular-docs

v1.2.3

Published

Publish angular documentation (ngdoc) to a gh-pages branch on Github

Downloads

5

Readme

angular-docs

standard-readme compliant

Publish angular documentation (ngdoc)

Background

Generate static documentation based on the ngdoc flavor of jsdoc.

Your documentation is complete when someone can use your module without ever having to look at its code. This is very important. This makes it possible for you to separate your module's documented interface from its internal implementation (guts). This is good because it means that you are free to change the module's internals as long as the interface remains the same.

Remember: the documentation, not the code, defines what a module does.

~ Ken Williams, Perl Hackers

Install

This project uses node and npm. Go check them out if you don't have them locally installed.

$ npm install --global @buildium/angular-docs

Usage

$ buildium-angular-docs --help
# Prints out the available commands and options

Programmatic API

var buildiumAngularDocs = require('@buildium/angular-docs');

buildiumAngularDocs({
    scripts: [ 'src/index.js' ],
    title: 'My AngularJS Docs',
    sourceFiles: [ '../src/**/*.js' ],
    destination: '../docs',
    ghPages: true
});

Contribute

Feel free to dive in! Open an issue or submit PRs.

angular-docs follows the Contributor Covenant Code of Conduct.

License

MIT © Buildium