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

ember-cli-typedoc

v1.1.1

Published

TypeDoc documentation generation for EmberCLI projects

Downloads

9

Readme

npm version CI Coverage Status

ember-cli-typedoc

TypeDoc documentation generation for EmberCLI projects.

Installation

ember install ember-cli-typedoc

Usage

Docs generation is opt-in via either environment variable or build config.

TYPEDOC=true ember start
// ember-cli-build.js
const EmberAddon = require('ember-cli/lib/broccoli/ember-addon');

module.exports = function (defaults) {
  return new EmberAddon(defaults, {
    'ember-cli-typedoc': {
      enabled: true,
    },
  });
};

Configuration

Out of the box, ember-cli-typedoc has a couple of loosely held opinions; you're free to interject your own as required. The parent project's /addon directory is the default entrypoint, with expand as the default interpretation strategy. Private, protected, internal annotated, and external super class members are ignored.

Any configuration offered by TypeDoc can be tweaked in the project's build config.

Both HTML and JSON outputs are generated to a /docs directory, by default. The out and json arguments properties can be unset to limit this.

For example, to include everything that is ignored by default while limiting your output to JSON:

const EmberAddon = require('ember-cli/lib/broccoli/ember-addon');

module.exports = function (defaults) {
  return new EmberAddon(defaults, {
    'ember-cli-typedoc': {
      enabled: true,
      excludeExternals: false,
      excludePrivate: false,
      excludeProtected: false,
      excludeInternal: false,
      out: null,
    },
  });
};