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-no-javascript

v1.0.3

Published

I recently found an eslint rule called [no-plusplus](https://eslint.org/docs/latest/rules/no-plusplus). It's based on the logic that this code—

Downloads

7

Readme

eslint-no-javascript

I recently found an eslint rule called no-plusplus. It's based on the logic that this code—

i
++
j

—increments j instead of i, which is confusing, so what we're going to do is ban the ++ operator. This logic is completely sound and reasonable, as are all the other eminently sensible rules that eslint enforces by default. If I have one criticism of them, it is that they do not go far enough. And to that end, I have created eslint-no-javascript, which enforces that developers must not use JavaScript. Any code in your source other than whitespace and comments will be rejected, and if you use the --fix option it will be removed.

JavaScript is the cause of most accessibility, usability, performance and security issues in modern webapps and its use is discouraged by all reputable experts. This plugin can remove this problem from all of your projects.

Examples of valid code

  
 
   

// This is not executable code

Examples of invalid code

const x = 4;

❌ Unexpected JavaScript

console.log("example")

❌ Unexpected JavaScript

function test() {
    let y = 2;
    return y;
}

test();

❌ Unexpected JavaScript

Usage

Install the package, and eslint itself:

npm install eslint eslint-no-javascript

You will not need any other eslint plugins, since all code they reject would be rejected by eslint-no-javascript, or indeed any other dependencies at all, since you will not be allowed to import them.

Add the package to your eslint.config.js file:

const noJs = require("eslint-no-javascript");

module.exports = [
    {
        files: ["**/*.js"],
        ignores: ["eslint.config.js"],
        languageOptions: {
            sourceType: "commonjs",
            ecmaVersion: "latest"
        },
        plugins: { "eslint-no-javascript": noJs },
        rules: {
            "eslint-no-javascript/no-javascript": "error"
        }
    }
];

Make sure to exclude eslint.config.js from the linter, or else eslint will delete its own configuration file.

Run eslint to check if you have used any JavaScript, and if you have then use eslint --fix to remove it.