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

@ezez/eslint-plugin-todo-task-id

v0.1.0

Published

Unstructured TODO or FIXME comments can lead to confusion ("what was this about?") and in result a "forever TODOs" in your codebase. By enforcing a standardized format, you:

Downloads

166

Readme

This ESLint plugin enforces a standardized format for TODO and FIXME comments, ensuring that they are always accompanied by:

  1. A descriptive comment that shortly explains what needs to be done.
  2. A bug tracker task ID formatted as [PREFIX-123] to reference the corresponding issue.

Why Use This Plugin?

Unstructured TODO or FIXME comments can lead to confusion ("what was this about?") and in result a "forever TODOs" in your codebase. By enforcing a standardized format, you:

  • Improve Traceability: Every comment links to a bug tracker task ID for easy follow-up.
  • Enhance Clarity: Descriptive comments make tasks self-explanatory, without visiting the bug tracker.
  • Maintain Quality: Avoid incomplete or vague TODO/FIXME entries.

Available Rules

This plugin provides just a single rule:

  • require-todo-task-number: Enforces a standardized format for TODO and FIXME comments.

To enable the rule, add it to your ESLint configuration file:

Old style config:

{
  "plugins": ["@ezez/eslint-plugin-todo-task-id"],
  "rules": {
    "@ezez/todo-task-id/require-todo-task-number": "error"
  }
}

Flat style config:

import todoTaskId from "@ezez/eslint-plugin-todo-task-id";

const config = [
    // other part of your config
    {
        name: "Todo Task ID plugin",
        plugins: {
            todoTaskId
        },
        rules: {
            "todoTaskId/require-todo-task-number": "error"
        }
    }
];

export default config;

Configure require-todo-task-number

The rule accepts an optional object with the following properties:

  • projectId (string): The bug tracker project ID to enforce in the format of 1 to 10 UPPER CASE a-z characters. When not given, the rule will accept any project ID.
  • projectIdFirst (boolean): When true, the project ID must come immediately after the TODO/FIXME keyword. Default is false, which allows the project ID to appear anywhere in the comment (on the same line).
  • minDescriptionLength (number): The minimum length of the description part of the comment. Default is 10, however this check can be disabled by setting it to 0.