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

@liquid-labs/sdlc-resource-eslint

v1.0.0-alpha.22

Published

Pre-configured formatting and style tool combining prettier and eslint.

Downloads

46

Readme

@liquid-labs/sdlc-resource-eslint

Pre-configured formatting and style tool combining prettier and eslint.

Formatting overview

  • The code is run through prettier first mainly because it does a much better job adding and removing line breaks to fit code within a target width (80 chars).[^1]
  • We then run the code through eslint for reformatting as well. This is because prettier is highly opinionated and we don't agree (nor think you should be forced to agree) with all the prettier opinions. In particular, our default configuration:
    • places operators at the beginning of the next line rather than the end of the previous line in multi-line expressions; e.g.:
    const foo = bar // our way
      && baz
    // vs
    const foo = bar && // prettier way
      baz
    Our approach is generally accepted to be more readable.
    • places else if/else/catch, etc. on a newline; e.g.:
    if { // our way
      ...
    }
    else {
    
    }
    // vs
    if { // prettier way
      ...
    } else {
    
    }
    While prettier's approach is more compact, we like the consistency of our approach and the ability to add ending comments associated with the preceding block.
    • aligns the colons in object declarations; e.g.:
    { // our approach
      foo           : 'hey',
      longFieldName : 'how are you?',
    }
    // vs
    { // prettier way
      foo : 'hey',
      longFieldName : 'how are you?',
    }
    Again, we think our approach is more readable and also just looks cool.
  • The dual-formatting is also compatible with the eslint configuration, so the code run through prettier + eslint for reformatting will also pass eslint when just checking (bot not changing) the code format.

[^1]: I remember eslint actually doing a better job of this, but for whatever reason (maybe when we upgraded to use the new '@stylistic' plugin that replaces the old core ruleset) we noticed two issues with the latest eslint based reformatting. First, it was miscounting the correct indention level where '(' was involved. Second, it seemed that eslint was failing to break up long lines automatically. (@stylistic/eslint-plugin: 2.6.4, eslint: 8.50.0)