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

coc-common-ui2

v0.1.0

Published

## Demoing your components

Downloads

1

Readme

coc-common-ui2

Demoing your components

You can add a demo folder in each of your component folders. In the demo folder you can add as many demos as you want. Each demo file will automatically be rendered and the source displayed.

In addition you can comment your code using JSDOC syntax. This information will then also be displayed in the documentation.

e.g.

/**
 * A showcase component, renders a react component and displays source code.
 *
 * @export
 * @param {string} demo - the react demo to be run
 * @param {string} source - the source code to be displayed
 * @return {object} Showcase Component
 */
const Showcase = ({ source, demo }) => ( ... );

NOTE:

  • Only comments with the @export tag will be shown in the documentation.
  • Only comments of a component with a demo will be shown.

To view your component documentation run:

npm start

Then open http://localhost:3000/ to see your library documentation.

Building your components

You can create a production ready website for your documentation with:

npm run build

To view the production ready documentation you can run:

npm install -g serve
serve -s build

Before publishing your library to npm, you will need to build it:

npm run build:dist

After running this command your library will be found in the dist folder.

Make sure you export your components from index.js. Only the components exported here will be part of your library.

Testing your components

Before publishing your components, the linter and tests will automatically run. You can also run them manually with:

npm run test

Publishing your library

You can easily deploy your library documentation to github pages. To do that, add the field homepage: <YOUR_GITHUB_PAGE_URL> to package.json.

Then run:

npm run deploy

You can publish your library to npm. To do that, simply run:

npm publish