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

@nivalis/linter

v0.0.15

Published

Lint your code with Biome and ESLint at once

Readme

@nivalis/linter

npm version License: MIT

Lint your code with Biome and ESLint at once

Overview

@nivalis/linter is a unified linting tool that combines the power of Biome and ESLint into a single, streamlined interface. Instead of running these linters separately, you can use @nivalis/linter to run both simultaneously and get consolidated results.

Features

  • Unified Interface: Run both Biome and ESLint with a single command
  • 🔄 Merged Results: Get consolidated linting results from both tools
  • 🛠️ Auto-fixing: Automatically fix linting issues with the --fix flag
  • 🔍 Debug Mode: Get performance metrics and detailed error information
  • Performance: Optimized for speed with caching enabled

Installation

# Using npm
npm install --save-dev @nivalis/linter

# Using yarn
yarn add --dev @nivalis/linter

# Using pnpm
pnpm add --save-dev @nivalis/linter

# Using bun
bun add --dev @nivalis/linter

Usage

# Basic usage
npx nivalis-linter "src/**/*.{js,ts,jsx,tsx}"

# With auto-fixing
npx nivalis-linter "src/**/*.{js,ts,jsx,tsx}" --fix

# With debug mode
npx nivalis-linter "src/**/*.{js,ts,jsx,tsx}" --debug

# Allow unsafe fixes
npx nivalis-linter "src/**/*.{js,ts,jsx,tsx}" --fix --unsafe

Configuration

@nivalis/linter uses your existing ESLint and Biome configurations. It will automatically detect:

  • ESLint configuration files (.eslintrc.*, eslint.config.js)
  • Biome configuration file (biome.json)

If no configuration is found, default configurations will be used.

Options

| Option | Description | Default | |-----------|-----------------------------------|---------| | --fix | Automatically fix linting issues | false | | --debug | Run in debug mode | false | | --unsafe| Allow unsafe fixes | false |

Why Use @nivalis/linter?

  • Save Time: Run both linters at once instead of separately
  • Unified Output: Get consolidated results in a single format
  • Best of Both Worlds: Benefit from both Biome's and ESLint's capabilities
  • Simplified Workflow: Integrate with your existing development process

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT