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

@mertcreates/eslint-plugin-mv3

v1.0.0

Published

ESLint rules for Manifest V3 extension safety (e.g., catching executeScript closure traps).

Downloads

37

Readme

eslint-plugin-mv3

npm version npm downloads license CI

ESLint rule(s) for MV3-safe scripting.executeScript usage.

It enforces that injected func code is self-contained, statically analyzable, and safe across Main World boundaries.

Contents

The Problem

When using Manifest V3 scripting.executeScript({ func }), the injected function is serialized and executed in Main World. Outer-scope values are not carried with it.

If injected code references variables outside its own scope, it can fail at runtime with ReferenceError: ... is not defined. This plugin catches those closure traps statically at lint time.

Features

  • Detects closure capture inside executeScript({ func })
  • Rejects imported/non-local func references
  • Enforces args: [...] when injected functions have parameters
  • Rejects dynamic/spread options that break static enforcement
  • Supports chrome and browser hosts
  • Supports alias/destructure/computed access, .call, .apply, .bind, Reflect.apply

Install

npm i -D @mertcreates/eslint-plugin-mv3
# or
yarn add -D @mertcreates/eslint-plugin-mv3
# or
pnpm add -D @mertcreates/eslint-plugin-mv3
# or
bun add -D @mertcreates/eslint-plugin-mv3

Usage (eslintrc)

{
  "plugins": ["@mertcreates/mv3"],
  "rules": {
    "@mertcreates/mv3/no-execute-script-closure": "error"
  }
}

Or use recommended config:

{
  "extends": ["plugin:@mertcreates/mv3/recommended"]
}

Usage (flat config)

import mv3Plugin from '@mertcreates/eslint-plugin-mv3';

export default [
  mv3Plugin.configs.recommended,
];

Rules

The recommended config enables this rule.

@mertcreates/mv3/no-execute-script-closure

Validates that:

  • func is local and resolvable in the same file
  • func does not capture outer-scope variables
  • args is present and array-literal when function parameters exist
  • invocation/config shape stays statically analyzable

Incorrect:

const TOP = 'outer';

function installBridge() {
  return TOP;
}

chrome.scripting.executeScript({
  target: { tabId: 1 },
  func: installBridge,
});

Correct:

function installBridge(source) {
  return source;
}

chrome.scripting.executeScript({
  target: { tabId: 1 },
  func: installBridge,
  args: ['outer'],
});

Options

No rule options right now. The rule is intentionally strict and zero-config.

Compatibility

  • ESLint: >=8.50.0 <10
  • Node: versions supported by your ESLint runtime

Benchmarks

Benchmarks separate:

  • ESLint core overhead
  • Rule-on cost
  • Net rule cost (rule-on - overhead)

Latest run highlights (BENCH_SCALE=1 BENCH_WARMUP=2 BENCH_RUNS=5):

  • noise-baseline-5k: net median rule cost ~2.96ms
  • mixed-worst-case (30k lines): net median rule cost ~16.19ms

See details in BENCHMARK.md.

License

MIT.