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

@pascaliske/eslint-config

v3.0.0

Published

Shared ESLint config for TypeScript projects.

Downloads

170

Readme

Shared ESLint config

npm (scoped) GitHub Tag Build Status License: MIT GitHub Last Commit Awesome Badges

Installation

To install the config use the following command:

yarn add @pascaliske/eslint-config --dev

For TypeScript projects you will also need the following peer dependencies:

yarn add eslint @typescript-eslint/{parser,eslint-plugin} --dev

For Angular projects you will also need the following peer dependencies:

yarn add eslint @typescript-eslint/{parser,eslint-plugin} @angular-eslint/{template-parser,eslint-plugin,eslint-plugin-template} --dev

Usage

There are three possible types of configurations available: base (only JS), typescript (JS + TS) and angular (JS + TS + Angular specifics). You can reference those by adding a suffix to the extends value in your config file (e.g. @pascaliske/eslint-config/angular). The base configuration will be used as default when the suffix is missing.

.eslintrc

{
  "root": true,
  "extends": "@pascaliske/eslint-config/base", // or typescript / angular
  "env": {
    "browser": true
  }
}

For usage in Node.js projects you can also enable the Node.js environment instead:

.eslintrc

{
  "root": true,
  "extends": "@pascaliske/eslint-config/base", // or typescript / angular
  "env": {
    "node": true
  }
}

For usage in TypeScript and Angular projects you have to use a JS based config file and explicitly set parser options with a tsconfig.json-file:

.eslintrc.js

module.exports = {
    root: true,
    extends: "@pascaliske/eslint-config/typescript", // or angular
    parserOptions: {
        project: `${__dirname}/tsconfig.json`,
        createDefaultProgram: true,
    },
    env: {
        node: true,
    },
}

For more information on environments visit the ESLint documentation.

License

MIT © 2022 Pascal Iske