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-highlight-temporary-code

v1.0.0

Published

Searches for @temp comment and throws out a warning.

Downloads

4

Readme

eslint-plugin-temporary-code

Problem :

Sometimes during development, we might change a dynamic logic to something static for testing out different scenarios without relying upon the application state.

What if we forget to revoke those temporary changes and unfortunately there is no unit test cases to catch it?

This plugin would help you remember those temporary code by throwing a eslint warning on it.

How it works

It searches for comments containing

@temp 

and warns about it. The user is expected to add a line of comment that contains @temp above or below his temporary code so that the plugin highlights it until its gone.

Installation

You'll first need to install ESLint:

npm i -D eslint

Next, install eslint-plugin-temporary-code:

npm i -D eslint-plugin-temporary-code

Usage

Add temporary-code to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

{
    "plugins": [
        "highlight-temporary-code"
    ]
}

Then configure the rule under the rules section.

{
    "rules": {
        "highlight-temporary-code/check-for-temporary-code": "warn"
    }
}

Example code :

In the code, while entering the temporary code statement add the comment @temp above or below it.

Let say,if we temporarily replace the below

const isPresent = someFunctioThatReturnsTrueOrFalse()

with

const isPresent = false

then replace it like

// @temp
const isPresent = false

or

/* @temp */
const isPresent = false

so that the plugin would know that this is the temporary code and throws a eslint warning.

Note :

It works in jsx with

{/* @temp */}

plugin-example-usage