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

esfmt

v0.0.15

Published

Javascript formatter library

Downloads

34

Readme

Build Status codecov.io npm version

esfmt formats (beautifies, pretty-prints) javascript (es6, jsx) code.

Install

npm install -g esfmt

CLI

Usage:
   esfmt [flags] [files ...]

Options:
   -w          | overwrite contents of the files with formatted version
   --help      | print this text
   --version   | print esfmt version

Without an explicit path, esfmt will process stdin and print results to stdout

Example

// echo 'if((a + b) * 4){return (e) => { return a.b.c(<Component a="5" b={[1, b, 0]}><br /></Component>)}} else { return {a: 5, b: 8, c: 9} }' | ./bin/esfmt
if ((a + b) * 4) {
    return (e) => {
        return a.b.c(<Component a="5" b={[1, b, 0]}>
            <br />
        </Component>);
    };
} else {
    return {
        a: 5,
        b: 8,
        c: 9
    };
}

Development

Testing

Most of the testing is done by formatting code snippets and matching resulting output with expected string value.

Code snippet files are located at test/code_snippets/*.js

The DSL has the following format

// input: test case description (e.g. variable declaration)
let a        =         5;
// output:
let a = 5;

this will produce a test case that will look like this:

code snippets
    ✓ code_snippets_filename: test case description (e.g. variable declaration)

if any specific test needs to be whitelisted (mocha it.only) or blacklisted (mocha it.skip) skip or only line can be added after the test description

// input: arrays
// skip
[1, 'a', null];
// output:
[1, 'a', null];

or

// input: arrays
// only
[1, 'a', null];
// output:
[1, 'a', null];

in addition to that, if any specific configuration values need to be used for the test, they can be passed using a config line // config: {"settingName": "value"}

Note that the values should be provided in JSON format (meaning double quotes around the keys)

// input: arrays
// only
// config: {"max-len": 5}
[1, 'a', null];
// output:
[1, 'a', null];

TODO

  • CLI
  • comments in
    • class definitions
    • arguments (lists)