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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@linusborg/eslint-config

v0.5.0

Published

Personal Eslint config presets

Readme

@linusborg/eslint-config

Personal presets used in my projects.

Included:

  • @typescript-eslint
  • compatible with prettier
  • eslint-plugin-unused-imports
  • Vue support (default)
  • modular approach to adjust for different environments

Usage

Common Usage example

Vue application with TypeScript. Also enables different globals for config files (ran in node) vs. app src code (ran in browser).

// eslint.config.js
import {
	vueConfig,
	browserGlobalsConfig,
	nodeGlobalsConfig,
} from '@linusborg/eslint-config'

export default [
	...vueConfig,
	{
		// for config files
		files: ['*.ts', '*.js'],
		...nodeGlobalsConfig,
	},
	{
		// for browser code
		files: ['src/**/*.ts', 'src/**/*.js', 'src/**/*.vue'],
		...browserGlobalsConfig,
	},
]

Exports

vueConfig

Use this if you're building a Vue based application, plugin or library that will involve SFCs.

baseConfig

Use this if you are building a library or application that does not involve Vue SFCs.

nodeGlobalsConfig

This adds node globals, so should be used with a file filter for config files.

{
	files: ['*.ts', '*.js'],
	...nodeGlobalsConfig,
}

browserGlobalsConfig

This should be combined with the vue or base config for the actual source files when your app/library will run in the browser.

{
	files: ['src/**/**ts', 'src/**/*.js', 'src/**/*.vue'],
	...browserGlobalsConfig,
}

sharedSSRGlobalsConfig

This should be combined with the vue or base config for the actual source files when your app/library will run in the browser AND the server.

{
	files: ['src/**/**ts', 'src/**/*.js', 'src/**/*.vue'],
	...sharedSSRGlobalsConfig,
}

globals

Re-export of the globals package, in case you need it for more custom configs.

see https://www.npmjs.com/package/globals