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

@axonteam/eslint-config-axonteam

v2.0.3

Published

Eslint config for all AxonTeam javascript projects

Downloads

8

Readme

eslint-config-axonteam

This is the global eslint config for all Axonteam javascript projects.
This configuration is not meant to be permissive, however, it aims to be fairly strict to guarantee consistent code style.

The philosophy is to comply to the linter when writing the code. It helps you writing cleaner and more efficient code. If there is something you really don't want to do like the linter says, you explicitly disable the rule or the line. This way, we make sure to reduce errors as much as possible, and that if you choose to ignore a rule you're fully aware.

All team projects should be using this configuration, however, everyone is welcome to use it.

Installations

This package is availabe on npm here.
Install this package with npm install @axonteam/eslint-config-axonteam or yarn add @axonteam/eslint-config-axonteam.
Make sure to have eslint already installed in your project.
Now simply create a .eslintrc.json file and add the following: "extends": "@axonteam/eslint-config-axonteam".

Contributions

Make sure to PR any rule that could be added using the samecode style idea. Nothing can ensure the pull request will be accepted but contribution is always welcome.