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-lucas-silbernagel

v2.1.0

Published

ESLint & Prettier configuration for React projects with TypeScript

Downloads

32

Readme

ESLint and Prettier config for React + TypeScript

To use in a project add it by using the following steps:

npx install-peerdeps --dev eslint-config-lucas-silbernagel

Use yarn instead of npm if prompted to do so.

Then, create a .eslintrc.js file in the root of your project's directory and add the configuration.

module.exports = {
  extends: ['eslint-config-lucas-silbernagel'],
}

Finally add these two scripts to package.json

{
    "scripts": {
        "lint": "eslint --ext \".js,.jsx,.ts,.tsx\" --ignore-path .gitignore .",
        "lint:fix": "eslint --fix --ext \".js,.jsx,.ts,.tsx\" --ignore-path .gitignore ."
    }
}

Depending on which project the package is being installed in, you may encounter dependency conflicts. To resolve, delete node_modules, yarn.lock, and package-lock.json. Also delete "eslint" from package.json if it exists. Then run yarn or npm install. If the project is dockerized, rebuild the Docker container. Depending on the project, further dependency conflict resolution may be necessary.

In VSCode, make sure you are not running the Prettier extension. The ESLint extension should be used instead, as this package bundles Prettier with ESLint, and can cause conflicts with the Prettier extension.

To lint all files at once, use the above scripts. Otherwise, linting issues can be resolved file by file.

To disable linting in any file add the following comment at the top:

/* eslint-disable */