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

@genie-solutions/eslint-config-genie

v1.3.0

Published

Standard eslint config for Genie Solutions projects

Downloads

220

Readme

ESLINT CONFIG GENIE

This is our shareable eslint configuration to be used for all JavaScript and TypeScript projects.

It enforces some sensible code styling guidelines and encourages consistency across our projects.

How to Use

run: npm install @genie-solutions/eslint-config-genie --save-dev

then create .eslintrc.js:

module.exports = {
  extends: [ "@genie-solutions/eslint-config-genie" ]
}

Contributing

Start by socialising the change you would like to make with other developers, and when it seems like the general consensus is that it would be a positive one, continue with this process.

  • Add an example file showcasing the practical implications of the change you would like to make. See the "Examples" section below for more details.
  • Make the necessary changes to the .eslintrc.js file.
  • Run the test suite to ensure your config changes have the desired effect. See the "Test Suite" section below for more details.
  • Open a merge request and get it merged.

Examples

The examples directory contains examples of good and bad code according to the eslint config.

It is intended to serve as a showcase of the practical application of the rules being enforced.

Try to keep the files related to a single rule or concept.

Sometimes there are errors or warnings which get in the way of simplicity, for example in the following code eslint will complain if you do not assign the array to a variable, and if you do assign it to a variable then it will complain that the variable is not used anywhere. It is obviously necessary to disable this warning to prevent writing a whole bunch of code which is not useful here.

// This allows expressions (like arrays and hashes / objects) without assigning or returning.
/* eslint-disable no-unused-expressions */
[{
    message1: 'hi',
    message2: 'bye',
}];
/* eslint-enable no-unused-expressions */

Test Suite

The test framework for this project is a bash script which runs the examples (in "examples" dir) through eslint. The "good" examples pass if no errors are raised, and the "bad" examples pass if errors are raised.

Simply execute test.sh to run the tests.

Deploying

TODO