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

@dzek69/eslint-config-import-typescript

v1.0.1

Published

These are my preferred Import Plugin code style linting rules. You'll probably hate them.

Downloads

12

Readme

eslint-config-import-typescript

These are my preferred Import Plugin code style linting rules. You'll probably hate them.

This is an TypeScript addition to "base" @dzek69/eslint-config-import package. Using this package alone doesn't make sense. Also you HAVE TO have @dzek69/eslint-config-typescript set up already.

Idea behind these

No tricks, no magic, no useless code, no complicated code. Very opinionated. Rules that duplicates features of IDEs are disabled.

Installation

Installation steps assumes you've already configured base eslint config, ie: installed my base rules. Installation steps also adds "base" eslint-config-import.

npm i eslint-plugin-import @dzek69/eslint-config-import @dzek69/eslint-config-import-typescript --save-dev

In your .eslintrc file add the rules in extends array:

{
  "extends": [
    "@dzek69/eslint-config-import-typescript"
  ]
}

It will automatically define proper plugin.

Then to lint src and test directories with subdirectories run:

npx eslint src test --ext .ts,.tsx,.js,.jsx,.mjs

Full config example

{
    "extends": [
        "@dzek69/eslint-config-base",
        "@dzek69/eslint-config-typescript",
        "@dzek69/eslint-config-import",
        "@dzek69/eslint-config-import-typescript"
    ],
    "env": {
        "node": true
    },
    "parserOptions": {
        "sourceType": "module"
    }
}

License

MIT