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

electrode-docgen

v1.0.1

Published

Electrode document generator

Downloads

5

Readme

Electrode Documentation Generator

A custom metadata extractor for the Electrode framework.

Before getting started, please make sure you read the React Developer Guide!

Running it

electrode-docgen --package ./package.json --src ./src --metadata components.json
electrode-docgen --package ./package.json --src ./src --markdown components.md

Or in package.json

  "scripts": {
    ...
    "generate": "npm run generate-metadata && npm run generate-documentation && npm run generate-demo",
    "generate-metadata": "electrode-docgen --package ./package.json --src ./src --metadata components.json",
    "generate-documentation": "electrode-docgen --package ./package.json --src ./src --markdown components.md",
    "generate-demo": "electrode-docgen --package ./package.json --src ./src --demo demo"
  }

Writing It

Standard Markdown format in the description.

Metadata

@component Fixie
@import {Fixie}

Private components

@private

Playgrounds

@playground
Fixie
``
<div>
</div>
``

And for noRender set to false.

@playground
Fixie
!noRenderFalse!
``
<div>
</div>
``

NOTE: In order to generate documentation correctly there should not be any statements between your documentation comment and React class declaration, for e.g.

// GOOD

const foo = [];

/*JSDoc comment*/

class Foo extends React.Component {...}
// BAD

/*JSDoc comment*/

const foo = [];

class Foo extends React.Component {...}

Auto generated demo

/// start imports
/// end imports
/// start render
/// end render

Issues

Before submitting an issue, please see the Issue Submission Guidelines

Contributing

If you're interested in contributing, see the React Developer Guide's Contribution Guide