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

most-cli

v1.0.2

Published

CLI utilities for working with Web Components and Polymer

Downloads

3

Readme

M.O.S.T.

A collection of CLI tools for working with Polymer Web Components.

Installation

$ npm i -g most-cli

or

$ yarn global add most-cli

Usage

$ cd <component-path> && most <command>

Commands

Command params can also be set in a .mostrc file placed in the component's root or any other parent directory.

1. css-api

$ cd your-component
$ most css-api

Params

|   Name       | Alias |                               Description                               |     Default | |:-------------- | :---- | :------------------------------------------------------------------------ | -------------------| |--file | f | File where the CSS properties will be searched. | <component>.html | |--docs | d | File where the CSS docs in markdown format will be searched. | <component>.html | |--sort | s | Set to true to sort CSS properties alphabetically. | false | |--unformatted | u | Set to true to render the markdown table without format (unaligned cells) | false |

The command compares your current CSS API docs inside your component's HTML (markdown table) with the CSS properties and mixins found in the component styles and prints a markdown table with all the properties found in your component styles. If a property is not documented previously in your docs, it will take the value used in styles.

The command also warns you about API diffs (new properties) and potentially BREAKING CHANGES (removed properties) that may require a major version upgrade for the component.

Used without params, it will search CSS properties and docs in <your-component-name>.html.
If you need to specify a different file for the styles, you can use the --file param. The placeholder {{component}} can be used instead of the component's name.

Example with custom path to styles:

$ most css-api --file {{component}}-styles.html

Example with custom path to docs:

$ most css-api --docs README.md

Screenshots

Default output
Screenshot of the default output

Added properties
Screenshot of the output with added CSS properties

Removed properties
Screenshot of the output with removed CSS properties

Unformatted table
Screenshot of the output with unformatted option

2. public-api

$ cd your-component
$ most public-api

The command writes a file (public-api.json) with the public properties, methods, events and CSS properties of the analyzed component.

This command can be useful to detect breaking changes in the component's API by comparing the generated file with the same file generated in a previous version (release) of the component.

Config file

.mostrc

You can set the the params used for each command in a .mostrc file that can be placed in the component's root or any other parent directory. This file allows to use placeholders like {{component}} that will be replaced by the component's name.

Example:

{
  "css-api": {
    "file": "{{component}}-styles.html",
    "docs": "README.md",
    "sort": false,
    "unformatted": true
  }
}