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

@jitesoft/eslint-config

v4.2.7

Published

Semi-standard bundled for simple modification by Jitesoft org.

Downloads

128

Readme

@jitesoft/eslint-config

npm (scoped) Known Vulnerabilities npm Back project

Semi-standard shareable config to make it easier to modify by Jitesoft organization.

Installation:

npm i --save-dev @jitesoft/eslint-config

yarn add --dev @jitesoft/eslint-config

Configurations

There are four configurations available:

default, node, browser, jsx and jest.

As expected, the Node and Browser configurations are set to use globals for the environment. The default configuration is a mixed node/web configuration, while the jest configuration is created for code which uses the jest test framework.

Usage

To extend the base/default config, just use the scoped name as such:

{
  "extends": "@jitesoft"  
}

To be able to use the other configurations, the whole name have to be included:

{
  "extends": "@jitesoft/eslint-config/jest"
}

QA

Q:
Why?

A:
For an organization it's easier to keep a bundle of configurations than using a million little packages in each package.json file. This package contains all the standards used by Jitesoft.
Further more, if we wish to change any rules, it's a lot easier to do that in our own package than propagate it through settings files in all repositories!

Q:
Why hard versions in the package.json file?

A:
To make sure that all the packages are in the exact version that we thought they where at each publish, the versions of the sub-packages have been set to exact versions. It's hard to test and make sure that everything works as intended in case some users use later or earlier versions (even if it is patch versions!) without knowing.

Q:
Why semistandard and not just standard?!

A:
Cause semicolon is best. Thats why!

Q:
Why spaces instead of tabs?!

A:
....