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

fs-default-project-config

v9.0.0

Published

Repo containing commons fox sports project linting configs and editor settings

Downloads

501

Readme

fs-default-project-config

Repo containing commons fox sports project configs

Usage

eslint

Installing

  1. Install as a dev dependency in your repo.

  2. Set up your .eslintrc.js file to extend ./node_modules/fs-default-project-config/resources/.eslintrc.js

    For all rules (standards & react specific):

    module.exports = {
        "extends": [
            "./node_modules/fs-default-project-config/resources/.eslintrc.js"
        ]
    };

    Excluding react specific rules:

    module.exports = {
        "extends": [
            "./node_modules/fs-default-project-config/resources/.eslintrc-files.js"
            "./node_modules/fs-default-project-config/resources/.eslintrc-standards.js"
        ]
    };

If using eslint/compat, ensure that you copy .browserslistrc to your project root, or set up a browserslist config

    "browserslist": [
        "last 2 versions",
        "Safari >= 8",
        "Explorer >= 11"
    ],

Updating Rules

As eslint is constantly having rules added or tweaked, pay attention to the relevant eslint or plugin version defined in package.json to determine which ruleset is being applied.

If you want to update the rules, look at eslint's / the plugin's changelog since the last release and ensure all new rules have a definition, deprecated rules are removed etc.

Remember any rules capable of breaking a CI build should be SEMVER versioned a breaking change. That means adding a new rule or even making a current rule stricter.

sass-lint

  1. Install as a dev dependency in your repo.

  2. Set up your .sass-lint.yml file to extend ./node_modules/fs-default-project-config/resources/.sass-lint.yml

    options:
        config-file: ./node_modules/fs-default-project-config/resources/.sass-lint.yml

All Others

  1. Copy desired contents from ./node_modules/fs-default-project-config/resources/

Dependencies

In addition to eslint itself, the following eslint plugin npm packages are required for these rules (if you exclude some rules you won't need all of these)

  • eslint-plugin-jsx-a11y
  • eslint-plugin-react
  • eslint-plugin-filenames