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-tlorent

v1.0.4

Published

ESLint and Prettier Config from Tim Lorent

Downloads

2

Readme

eslint-config-tlorent

To install the peer dependencies (ESLint & TypeScript) and the necessary dependencies (ESLint plugins):

npx install-peerdeps --dev eslint-config-tlorent

extends

Create a new file eslint.rc in the root of your project (useful if you plan to add your own rules, otherwise package.json can become a mess) or add a new entry in package.json (if you are just extending this config):

eslint.rc

{
    "extends": "tlorent",
    "rules": {
        "yourOwnRule": "rule",
        "etc": "etc"
    }
}

package.json (if you used Create-React-App or Gatsby, there might already be an "eslintConfig" entry. Remove and replace).

{
    "eslintConfig": {
        "extends": "tlorent"
    }
}

Commit hooks

Add commit hooks to prevent 💩💩💩 from slipping into your codebase. -- lint-staged

npx mrm lint-staged

After running above command, this is a possible config for commit hooks:

"scripts": {
    "typecheck": "tsc --project . --noEmit"
},
"husky": {
    "hooks": {
      "pre-commit": "npm run typecheck && lint-staged"
    }
},
"lint-staged": {
    "*.{js,ts}?(x)": [
        "eslint --fix",
        "prettier --write"
    ]
}

TSConfig

Add a tsconfig.jon file in the root of your project. You can do this with npx tsc --init and then modify the generated config file or use this example config:

{
    "compilerOptions": {
        "target": "es5",
        "module": "commonjs",
        "jsx": "react",
        "sourceMap": true,
        "outDir": "./lib",
        "noEmit": true,
        "strict": true,
        "noImplicitAny": true,
        "strictNullChecks": true,
        "noUnusedParameters": true,
        "noImplicitReturns": true,
        "esModuleInterop": true,
        "skipLibCheck": true,
        "forceConsistentCasingInFileNames": true
    },
    "include": ["src"]
}