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-mskcc-dev

v2.0.0-beta.0

Published

MSKCC base eslint config

Downloads

2

Readme

eslint-config-mskcc-dev

GitHub tag (latest SemVer) GitHub issues GitHub closed issues GitHub pull requests GitHub closed pull requests

DEVELOPMENT REPOSITORY

This package provides MSKCC base eslint configurations to keep consistency with all our teams. Use this as the base to your project. These configurations will be continuously updated.

Usage

// create `.eslintrc` file in your project's root folder and add

{
  "extends": "mskcc"
}

Current configurations:

| Type | "extends" path | Description | |---|---|---| | ES6+ | mskcc | ESM config | | React | mskcc/react | ReactJS specific config | | React with TypeScript | mskcc/react-typescript | ReactJS, TypeScript, uses eslint-config-prettier, eslint-plugin-prettier, eslint-plugin-react, eslint-plugin-react-hooks, @types/eslint, @typescript-eslint/eslint-plugin, @typescript-eslint/parser | | Vue | mskcc/vue | Vue 2, uses eslint-plugin-vue , vue-eslint-parser |

Contribution

Request configurations

We are developing based around consistency throughout all engineers. If there are settings that you feel would benefit the community as a whole, please add your request using the link above.


@rushstack/eslint-patch

Making external plugins a dependency so the user don't have to manually install the plugins.

https://www.npmjs.com/package/@rushstack/eslint-patch

How to use it

Add a require() call to the to top of the .eslintrc.js file for each project that depends on your shared ESLint config, for example:

.eslintrc.js

require("@rushstack/eslint-patch/modern-module-resolution");

// Add your "extends" boilerplate here, for example:
module.exports = {
  extends: ['@your-company/eslint-config'],
  parserOptions: { tsconfigRootDir: __dirname }
};