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

postcss-docs

v0.1.0

Published

PostCSS doc comments

Downloads

4

Readme

PostCSS Docs

PostCSS plugin for doc comments.

/**
 * More complex doc
 *
 * @var {Color} --foo-color The value used as "color"
 */
.foo {
  color: var(--foo-color, currentColor);
}

After processing the above css source the result AST will contain additional information extracted from the parsed comments. Parsing is not part of the implementation of this package! Parsing is done using comment-parser. Both, the targeted Rule node as well as the Comment node will contain a doc field after the processing is done.

{
  "description": "More complex doc",
  "text": "/** ... */",
  // postcss ChildNode, can be null
  "target": { ... },
  "tags": [
    {
      "tag": "var",
      "description": "The value used as \"color\"",
      "name": "--foo-color",
      "type": "Color",
      "optional": false
      ...
    }
  ],
  // from comment-parser
  "source": [ ... ],
  // from comment-parser
  "problems": [ ... ]
}
Useful Links

Usage

Step 1: Install plugin:

npm install --save-dev postcss postcss-docs

Step 2: Check you project for existed PostCSS config: postcss.config.js in the project root, "postcss" section in package.json or postcss in bundle config.

If you do not use PostCSS, add it according to the official docs.

Step 3: Add the plugin to your config

module.exports = {
  plugins: [
+   require('postcss-docs')
  ]
}