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 🙏

© 2025 – Pkg Stats / Ryan Hefner

clolint-js

v0.1.1

Published

parsing and linting of Clojure code

Downloads

5

Readme

clolint-js

Quick start

$ git clone [email protected]:mattfenwick/clolint-js
$ cd clolint-js
$ cat clj/examples.clj | node index.js > output.json

Overview

A tool for sanity checking Clojure code, by parsing it and performing various static analyses. I wrote it to help me learn Clojure -- it finds my stupid mistakes!

Examples

Parse errors such as mismatched or unmatched braces generate traces of line/column information, indicating what the parser was working on when it failed:

$ echo '(a b c' | node index.js

    {
      "status": "error",
      "value": {
        "phase": "parsing",
        "error information": [
          ["clojure", [1, 1]],
          ["list", [1, 1]],
          ["close", [2, 1]]
        ]
      }
    }

Domain checks of forms -- i.e. do the values satisfy Clojure constraints:

$ echo '{:a} \newlin ^ 3 []' | node index.js

    {
      "status": "success",
      "value": [
        {
          "number": 1,
          "severity": "error",
          "message": "uneven number of elements in table",
          "position": [1, 1]
        },
        {
          "value": "newlin",
          "severity": "error",
          "message": "invalid long char",
          "position": [1, 6]
        },
        {
          "type": "integer",
          "severity": "error",
          "message": "invalid metadata type",
          "position": [1, 16]
        }
      ]
    }

Special form syntax:

$ echo '(def x :docs 4)' | node index.js

    {
      "status": "success",
      "value": [
        {
          "severity": "error",
          "name": "def",
          "message": "in 4-arg version, doc-string must be a string",
          "position": [1, 8]
        }
      ]
    }

Anonymous functions and arguments:

$ echo '%x #(%a)' | node index.js

    {
      "status": "success",
      "value": [
        {
          "symbol": "%x",
          "severity": "warning",
          "message": "%-args should not be used outside of #-shorthand functions",
          "position": [1, 1]
        },
        {
          "error": [["token", [1, 7]]],
          "text": "%a",
          "severity": "error",
          "message": "invalid %-arg",
          "position": [1, 6]
        }
      ]
    }


$ echo '#(a #(b %1) %)' | node index.js

    {
      "status": "success",
      "value": [
        {
          "positions": [[1, 1]],
          "severity": "error",
          "message": "nested shorthand function",
          "position": [1, 5]
        }
      ]
    }

(TODO) Macro and function syntax

$ echo '(fn)' | node index.js

... TODO ...

(TODO) Indentation

(TODO) Symbol definitions: unused, undefined, redefined, shadowed

Other resources

License

MIT. Please don't use it for evil.

Contributing

Features, patches, ideas, corrections are all welcome!