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

@zeitonline/eslint-config

v3.1.1

Published

Common eslint config for DIE ZEIT

Readme

@zeitonline/eslint-config

This package provides a shared Eslint configuration for projects at DIE ZEIT.

This is an ESM-only package.

Installation & Usage

1. Install the package

For example using npm:

npm install --save-dev @zeitonline/eslint-config

2. Create or update the eslint.config.js file

Add an eslint.config.js (or .ts) file to the root of your project and extend the shared configuration. You can choose to use the base configuration or the Svelte-specific configuration:

Base Config

Intended for all JS or TS projects.

For JavaScript Projects (Default)
import zonEslintConfig from '@zeitonline/eslint-config';

export default [
	...zonEslintConfig, // or zonEslintConfig.js
	{
		// Add your project-specific overrides here
	},
];
For TypeScript Projects
import zonEslintConfig from '@zeitonline/eslint-config';

export default [
	...zonEslintConfig.ts,
	{
		// Add your project-specific overrides here
	},
];
Svelte Config

Intended for Svelte or SvelteKit projects. This config extends the base config and adds Svelte-specific plugins and rules.

For JavaScript Svelte Projects (Default)
import zonEslintConfigSvelte from '@zeitonline/eslint-config/svelte';

export default [
	...zonEslintConfigSvelte, // or zonEslintConfigSvelte.js
	{
		// Add your project-specific overrides here
	},
];
For TypeScript Svelte Projects
import zonEslintConfigSvelte from '@zeitonline/eslint-config/svelte';

export default [
	...zonEslintConfigSvelte.ts,
	{
		// Add your project-specific overrides here
	},
];
Type-Aware Rules

Use .tsTypeChecked instead of .ts (base and Svelte) to enable the type-aware rules of typescript-eslint. Run ESLint from the folder containing your tsconfig.json.

.ts no longer creates type information for Svelte files, so type-aware Svelte rules such as svelte/no-unused-props do nothing there. Use .tsTypeChecked to keep them.

In SvelteKit, run svelte-kit sync before linting, otherwise ./$types resolve as any. TS files outside your tsconfig.json (e.g. vitest.setup.ts) fail to parse; add them to include.

Vitest Config

Install @vitest/eslint-plugin and add ...zonEslintConfigVitest from @zeitonline/eslint-config/vitest to your config.

To also ignore everything in your .gitignore, add includeIgnoreFile() from @eslint/compat.

3. (Optional) Add a lint script to your package.json

To conveniently lint your files you may add a new script to your package.json:

{
	"scripts": {
		"lint": "eslint ."
	}
}

Further Reading