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

@splunk/eslint-config

v6.0.0

Published

Standardized Splunk ESLint configuration

Readme

@splunk/eslint-config

This package provides extendable ESLint configuration objects. Currently, the following configs are available:

Available configs

Requires Babel:

  • browser - For code that runs in the browser.
  • browser-prettier - For browser code that is formatted by prettier.
  • node - For node scripts.
  • node-prettier - For node scripts that are automatically formatted with prettier.

Does not require Babel - use these if your build tool handles JSX natively:

  • flat-browser - For modern toolchains (Vite + SWC, etc.) without Babel.
  • flat-browser-prettier - For browser code with modern toolchains, formatted with prettier.

Install

  1. Install the package and its required peers:
    npm install --save-dev @splunk/eslint-config eslint@^9 @eslint/js@^9
  2. If you are using the Babel-based configs, also install:
    npm install --save-dev @babel/core@^7 @babel/eslint-parser@^7

Usage

CommonJS flat config

Use the CommonJS entrypoints from eslint.config.cjs when you want the Babel-based browser config or the node configs.

const { defineConfig } = require('eslint/config');
const browser = require('@splunk/eslint-config/browser');

module.exports = defineConfig(browser, {
    // Your additional configuration
});
const { defineConfig } = require('eslint/config');
const browserPrettier = require('@splunk/eslint-config/browser-prettier');

module.exports = defineConfig(browserPrettier, {
    // Your additional configuration
});
const { defineConfig } = require('eslint/config');
const node = require('@splunk/eslint-config/node');

module.exports = defineConfig(node, {
    // Your additional configuration
});
const { defineConfig } = require('eslint/config');
const nodePrettier = require('@splunk/eslint-config/node-prettier');

module.exports = defineConfig(nodePrettier, {
    // Your additional configuration
});

ESM Babel-free browser config

Use the flat-browser entrypoints from eslint.config.js / eslint.config.mjs when your toolchain handles JSX without Babel.

import splunkConfig from '@splunk/eslint-config/flat-browser.mjs';

export default [
    ...splunkConfig,
    // Your additional configuration
];
import splunkConfig from '@splunk/eslint-config/flat-browser-prettier.mjs';

export default [
    ...splunkConfig,
    // Your additional configuration
];