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 🙏

© 2026 – Pkg Stats / Ryan Hefner

eslint-plugin-no-restricted-globals-scope-aware

v1.0.0

Published

ESLint rule to restrict globals with proper scope awareness, working around TypeScript namespace declarations

Readme

eslint-plugin-no-restricted-globals-scope-aware

ESLint rule to restrict globals with proper scope awareness. Unlike the built-in no-restricted-globals, this rule correctly handles cases where TypeScript namespace declarations confuse ESLint's scope analysis.

The Problem

When you have TypeScript type declarations like:

declare global {
    namespace foobar { ... }
}

The built-in no-restricted-globals rule won't trigger because ESLint sees foobar as "defined" by the namespace declaration.

The Solution

This plugin uses ESLint's scope analysis to check if there's an actual local variable declaration (with an initializer). This allows you to enforce a pattern where direct global access is prohibited, but access through a local variable is allowed.

The Wrapper Pattern

Create a simple wrapper function that returns the global:

// getFoobar.ts
export function getFoobar(): typeof foobar {
    return foobar; // eslint-disable-line no-restricted-globals-scope-aware/no-restricted-globals-scope-aware
}

Then in your code, use the wrapper to create a local variable:

import { getFoobar } from "./getFoobar";

const foobar = getFoobar();

// Now foobar.doSomething() won't trigger the rule
// because 'foobar' refers to the local variable, not the global
foobar.doSomething();

This pattern:

  • Centralizes global access to a single location (easier to mock/test)
  • Makes dependencies explicit via imports
  • Allows the linter to catch accidental direct global usage

Installation

npm install eslint-plugin-no-restricted-globals-scope-aware --save-dev

Usage

Add to your .eslintrc:

{
    "plugins": ["no-restricted-globals-scope-aware"],
    "rules": {
        "no-restricted-globals-scope-aware/no-restricted-globals-scope-aware": [
            "warn",
            { "name": "foobar", "message": "Use const foobar = getFoobar(); instead" },
            "someOtherGlobal"
        ]
    }
}

Options

The rule accepts an array of restricted global names. Each item can be:

  • A string (the global name)
  • An object with name and optional message properties

License

MIT