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

@endosome/eslint-config-googleappsscript

v1.0.1

Published

Shared ESLint 10 flat config for Google Apps Script projects, built on @endosome/eslint-config-node

Readme

@endosome/eslint-config-googleappsscript

A shared ESLint flat config for Google Apps Script projects, written in TypeScript or JavaScript (for example with clasp). It is @endosome/eslint-config-node with the changes below, so a Node.js project and an Apps Script project share one set of rules. ESLint 10 only.

Requirements

  • ESLint ^10.0.0
  • Node.js >=22.18.0
  • TypeScript >=4.8.4 <6.1.0 (typescript-eslint does not support TypeScript 7 yet)

Usage

npm install --save-dev eslint typescript @endosome/eslint-config-googleappsscript
// eslint.config.js
export { default } from '@endosome/eslint-config-googleappsscript';

The export is an array of flat config objects, so project rules go after it:

import config from '@endosome/eslint-config-googleappsscript';

export default [...config, { ignores: ['src/**/*.js'] }];

See the README of @endosome/eslint-config-node for everything that is inherited (plugins, type-aware linting, the rules that differ from the earlier ESLint 8 config).

What is different from the Node.js config

| | | |---|---| | Top-level declarations are never "unused" | Google calls menu handlers, triggers and web app entry points by name. @typescript-eslint/no-unused-vars skips variables, functions and imports at the top level of a file (vars: 'local') and still reports unused variables inside functions. Parameters, caught errors, destructured array items and variables that start with _ are ignored. | | TypeScript files are CommonJS scripts | sourceType: 'commonjs', so the top level of a file is not a module scope, whatever "type" the package.json has. | | Modules provided by the build resolve | import-x/no-unresolved ignores bare specifiers that start with a capital letter, such as import { x } from 'GoogleSpreadsheets'. npm package names cannot have capitals, so those are modules the build supplies. Other missing modules are still reported. | | HTML sidebars and dialogs are linted as browser scripts | .html files get the same rules (no n/*, vars: 'local') and sourceType: 'script', so a function that the markup calls from onclick is not "unused". | | No Node.js rules | The n/* rules are off, and the Node.js globals (process, require, setTimeout, URL, ...) are not defined. | | JavaScript files are scripts | sourceType: 'script' and no-undef with the Apps Script globals: the services (SpreadsheetApp, GmailApp, Logger, Utilities, ...), console and the advanced services. TypeScript is checked by tsc instead. | | No module-only rules | unicorn/prefer-module and unicorn/prefer-top-level-await are off. |

Things to know

  • Unused imports are not reported. The same vars: 'local' setting that lets entry points pass also skips imports at the top level. Use tsc with noUnusedLocals if you want to catch those.
  • A project override of @typescript-eslint/no-unused-vars replaces these options. If a project sets the rule itself, repeat vars: 'local': ['error', { vars: 'local', argsIgnorePattern: '^_', varsIgnorePattern: '^_' }].
  • .gs files are not linted, only .js, .ts and their variants (clasp 3 uploads .js).
  • Generated JavaScript next to the TypeScript sources (for example from a build step) is linted like any other file; add it to ignores.

Globals

globals.js lists the global variables that @types/google-apps-script declares. It is generated by npm run generate, and a test fails when it is out of date with the installed types.

License

MIT.