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-config-mns-core

v1.0.6

Published

Default ESLint config of FEAR Core extending eslint:recommended

Downloads

18

Readme

MNS Core ESLint configuration

This repository contains the default linting configuration which is recommended to be used in any MNS projects.

It is very important to avoid cryptic runtime errors due to linting issues, followed by tedious, time consuming debugging.

Accommodating a common coding style using strict linting rules also helps us developers to understand others' code much quicker.

Default rule set

The default configuration extends the eslint:recommended rules which can be found here. All rules marked as recommended are used, there are further rules added to the default Core config, take a look the common-config.js for details.

Available configurations

There are three separate configurations exported as node modules:

  • common
  • node
  • browser

The node and browser configurations extend the common one, but all can be used as a shared config.

The node configuration is intended to use in Node.js projects e.g. Gulp task implementation, whereas the browser should be a baseline for browser based projects e.g. FEAR pages.

How to use a configuration in your project

ESLint provides a way to create multiple shareable configurations which approach is used in this package.

In order to use the exposed configurations as defaults, first add the package to your project via:

$ npm install --save-dev mns-core-eslint-config

then the configurations will be available for extending in your own .eslintrc

// .eslintrc in your project's root
{
    "extends": "mns-core/browser-config"

    // override any rules here...
}