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

@dvsa/eslint-config-ts

v3.0.1

Published

Shareable ESLint config for Node/Typescript projects

Downloads

8,499

Readme

eslint-config-ts

Shareable ESLint config for use in Node/Typescript projects.

Why?

Rather than having to copy linter config files across code repos of the same project/tech stack, can pull in a standard shared config and dependencies from a single place and manage any changes/updates centrally.

Rules

This config uses:

  • Airbnb style guide rules (adapted for Typescript): https://github.com/airbnb/javascript
  • ESLint Typescript plugin recommended rules: https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/eslint-plugin
  • ESLint security plugin rules: https://github.com/nodesecurity/eslint-plugin-security

A few of the default rules are switched off/customised as specified in the config in index.js.

Developers

When making changes to this package you are unable to npm link to test the package locally due a bug in npm where peer dependencies are not installed. Github Issue - https://github.com/npm/cli/issues/2339

Prerequisites

  • >= npm 7.x.x

If the following dependencies are not present in your package.json, this package will install them (see peerDependencies in package.json):

eslint
@typescript-eslint/eslint-plugin
@typescript-eslint/typescript-estree
eslint-config-airbnb-typescript
eslint-plugin-import
eslint-plugin-jsx-a11y
eslint-plugin-react
eslint-plugin-react-hooks
eslint-plugin-security
eslint-plugin-jest

Usage

  1. Install the config in your project. npm install --save-dev @dvsa/eslint-config-ts

  2. Add a .eslintrc to your project root extending the config:

{
	"extends": "@dvsa/eslint-config-ts"
}

If you need to override the shared config in any way to suit your specific project, for example by customising certain rules, you can do so here. See the ESLint documentation for details.

  1. Add a .eslintignore to specify any project directories/files to exclude from the linter. ESLint already ignores node_modules by default.

  2. Run the linter: (npx) eslint --ext .js,.ts .

The --ext option is required to tell ESLint to lint .ts files (lints only .js by default) and . specifies the files/directory to lint.

If you are using VSCode, you can add the ESLint extension to see lint issues as you type. You might also want to add a pre-push hook to your project such that the linter runs on pushing code and fails the push if there are unresolved issues.


This shared config was originally made by the FTTS (Future Theory Test Service) team for use across our different project repos using a Node/Typescript/Jest stack. To suit your project you may need to configure the env property in your .eslintrc for your specific tech stack.