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

eslint-plugin-levitate

v8.0.0

Published

A set of useful ESLint rules

Downloads

1,169

Readme

Note that 🔧 indicates the rule is auto-fixable.

|Rule|Description| |---|---| |comment|enforce starting a single-line comment with either TODO:, HACK:, See {url}, or a first-capitalized word| |consecutive-block-new-line 🔧|enforce having a new line at the end of a non-last block and the other way around| |export-name-after-file-name|enforce naming a default exported identifier after the file name| |import-convention|enforce naming imported identifiers after the user-defined list| |import-name-after-file-name|enforce naming a default imported identifier after the file or the directory name (for an index file)| |import-path-from-closest-index|enforce writing an import path pointing to the closest index file| |import-path-without-mentioning-index 🔧|enforce writing an import path to an index file without mentioning "index.js"| |no-shortened-identifier|enforce naming an identifier without the user-defined abbreviations| |no-top-level-require|enforce writing no top-level require| |parameter-new-line 🔧|enforce having consistent new lines between parameters| |promise-all-with-static-array|enforce passing a static array to Promise.all()| |react-export-default 🔧|enforce writing React components consistently| |react-new-line 🔧|enforce having an additional empty line between two React elements if both of them occupy multiple lines| |react-prop-type|enforce writing type definition for React props| |react-sort-props 🔧|enforce consistent React props sorting| |require-name-after-file-name|enforce naming an identifier after the file name of its require statement| |require-name-after-predefined-name 🔧|enforce naming an identifier after the user-defined list of its require statement| |sort-imports 🔧|enforce sorting import statements. By default, this will sort according to Renke| |test-case-group 🔧|enforce using a function reference as a test case description| |test-case-new-line 🔧|enforce having a new line between it, test, describe and before expect function calls; this applies to *.{test,spec} files only| |test-case-title|enforce writing consistent test case titles for it and test function calls; the allowed pattern of the test case title is "(does not) return/render/call/fetch/set/throw(s) ... (, given ...)"; this also disallows writing some vague words, such proper, correct, appropriate, accurate, perfect| |typescript-enum-name|enforce naming enumerations consistently; the possible options are "PascalCase" (default), "camelCase", "UPPERCASE", "SNAKE_CASE"| |typescript-explicit-return-type|enforce functions to have explicit function return types| |typescript-exported-interface|enforce exporting an interface, unless it is inside a declare block| |typescript-method-type 🔧|enforce writing function types using arrow notation|