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

metal-soy-critic

v2.4.0

Published

A metal-soy code validation utility.

Downloads

24

Readme

metal-soy-critic

Build Status

A utility for validating your metal-soy components. This tool is not meant to do the same work that your javascript or soy compiler already does. Instead it checks for anti-patterns in your components.

Usage

First install mcritic from npm:

$ npm install -g metal-soy-critic

Then pass it a directory containing soy files that you would like to check:

$ mcritic src

You can also ignore files matching a particular glob:

$ mcritic . --ignore "**/{node_modules,classes,build}/**"

Configuration

By default, mcritic will recursively search the current and parent folders for a .soycriticrc.json file from the current working directory. Here is an example:

{
  "callToImport": [
    {
      "regex": "(\\S+)",
      "replace": "{$1|param}"
    }
  ]
}

Here are the currently supported settings:

callToImport

This property is used to provide a list of replacement configurations. Each list item must contain two properties:

  • regex

    This property is used to provide matches for replace. This should be a standard javascript regex that contains capture groups to be referenced in replace.

  • replace

    This property uses match groups defined in regex to translate a component name in a soy template to its corresponding import name when validating their import.

    When referencing match groups from regex, interpolation should be in the form of {$n}, where n is the match group number. An example would be "{$1}.js".

    Interpolations can also contain named string transformations delimited by a |. This transformation corresponds to the functions provided by change-case.

    Examples:

    • "{$1|lower|snake}.js"
    • "{$2}-{$1}"
    • "{$1|dot}.js"

|Type|Default| |----|-------| |array|"[{"regex": "(.*)", "replace": "{$1}"}]"|

implicitParams

This property is used to provide implicit params when checking if a Soy param is present in a component's STATE configuration. Here is an example:

{
  "implicitParams": {
    ".*Clay": ["visible", "elementClasses"],
    "DropDown": "open"
  }
}

Each key shoud be a valid RegExp string, which will be used to match a class name in your project. When a match is found, the value (which should be a string or Array<string>) will be added to the available params for that class when compared against it's Soy file.

|Type|Default| |----|-------| |object|{}|

Contributing

Feature requests, issues, and pull requests are welcome!