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-toplevel

v1.1.0

Published

An eslint plugin for disallow side effect at module toplevel

Downloads

1,300

Readme

eslint-plugin-toplevel

An eslint plugin for disallow side effect at module toplevel

Why?

Side effect in toplevel of a module are hard to reason, and behave diffrently in CommonJS and ES6 modules. And there is no way to import a module without it's side effects. Solution is simple: Don't make side effect at top level.

Example

Bad

console.log('hello world');
let s=0;
for (let i=0;i<10;i++) {
  s += i;
}
console.log(s);
fetch('/api').then(res=>res.text()).then(console.log);

Good

export async function main() {
  console.log('hello world');
  let s=0;
  for (let i=0;i<10;i++) {
    s += i;
  }
  console.log(s);
  const res = await fetch('/api');
  console.log(await res.text());
}

And then in html:

<script type="module">
  import { main } from "/js/main.mjs";
  main();
</script>

Or in nodejs make a runner.mjs file:

import { main } from "./main.mjs";
main();

Rules

There are three rules in this plugin:

no-toplevel-var

Disallow var usage at toplevel module.
Goal of this rule is to prevent modules to have internal state.

no-toplevel-let

similiar to no-toplevel-var

no-toplevel-side-effect

Disallow any side effect at top level

Contributing

I'd love to accept your patches and contributions to this project.
There are many ways you can contribute. For example:

  • Add tests
  • Fix bugs
  • Add option to ignore module.exports assigns in no-toplevel-side-effect rule
  • Add good documention