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-plugin-require-explicit-generics-kjj

v1.0.1

Published

Force configured functions to include explicit generics

Downloads

6

Readme

eslint-plugin-require-explicit-generics

Allow configured functions to require explicit generics.

Why?

Some libraries are over-permissive with their types, allowing generics to be omitted defaulting them to the any type. To prevent accidentally relying on this behaviour: this plugin allows you to specify a list of functions and constructors that MUST have explicit generics set.

Example

If you list myFunction in your .eslintrc.js:

myFunction(); // ❌ ESLint: Function 'myFunction' must be called with explicit generics...
myFunction<SomeType>(); // ✅ ESLint: Pass

Installation

First install ESLint:

# npm 
npm install eslint --save-dev
# yarn 
yarn add eslint --dev

Next, install eslint-plugin-require-explicit-generics

# npm
npm install eslint-plugin-require-explicit-generics --save-dev
# yarn
yarn add eslint-plugin-require-explicit-generics --dev

Configuration (REQUIRED)

In your .estlintrc.js add "require-explicit-generics" to the plugin list.

plugins: [
  "require-explicit-generics",
],

Then in the rules section set "require-explicit-generics/require-explicit-generics" pass the log level (either "error" or "warning"), then the list of functions to check.

rules: {
  "require-explicit-generics/require-explicit-generics": [
    "error",
    // List your functions here
    [ "myFunction", "myVar.myOtherFunction" ]
  ]
},

You can also use a map to define how many generics to expect for each function.

rules: {
  "require-explicit-generics/require-explicit-generics": [
    "error",
    { "myFunction": 3, "myVar.myOtherFunction": 1 }
  ]
},
myVar.myOtherFunction(); // Function 'myVar.myOtherFunction' must be called with generics...
myFunction<TypeA>(); // Function 'myOtherFunction' called with too few explicit generics...