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

@vyriy/browserslist-config

v0.7.7

Published

Shared Browserslist config for Vyriy projects

Readme

@vyriy/browserslist-config

Shared Browserslist config for Vyriy projects.

Purpose

This package centralizes reusable Browserslist target sets for applications and libraries in the Vyriy monorepo. It provides separate environments for local development, SSR, default production builds, and a narrower modern browser target. This keeps browser and runtime targets consistent between local development, client-side production bundles, modern builds, and server-side rendering.

Install

With npm:

npm install -D @vyriy/browserslist-config

With Yarn:

yarn add -D @vyriy/browserslist-config

Install browserslist separately only when the consumer project needs the Browserslist CLI binary.

Usage

Create .browserslistrc in your project:

[development]
extends @vyriy/browserslist-config

[ssr]
extends @vyriy/browserslist-config

[production]
extends @vyriy/browserslist-config

[modern]
extends @vyriy/browserslist-config

The same shared config is used for each environment, while Browserslist resolves the actual target list from the selected environment.

Environments

Available environments:

  • development
  • ssr
  • production
  • modern

Typical usage:

  • development for fast local builds and debugging.
  • production for public client bundles shipped to users.
  • ssr for Node.js server-side rendering or server-side build output.
  • modern for evergreen-browser-only builds, documentation, or experiments.

Programmatic usage is also supported:

const browserslistConfig = require('@vyriy/browserslist-config');

module.exports = browserslistConfig;
import browserslistConfig from '@vyriy/browserslist-config';

export default browserslistConfig;

If you use it from TypeScript, the package also exposes types from the root entry.

import browserslistConfig, { type BrowserslistConfig } from '@vyriy/browserslist-config';

const config: BrowserslistConfig = browserslistConfig;

CLI

You can inspect the resolved browser targets from the command line with browserslist:

npx browserslist --config .browserslistrc
npx browserslist --config .browserslistrc --env development
npx browserslist --config .browserslistrc --env ssr
npx browserslist --config .browserslistrc --env production
npx browserslist --config .browserslistrc --env modern

API

  • development targets the latest Chrome for fast local iteration.
  • ssr targets Node.js 24 for server-side rendering.
  • production targets a broad, safe browser baseline for public builds.
  • modern targets the latest Chrome, Safari, and Firefox versions.

Full Example

See the article with resolved target examples for each environment: https://vyriy.dev/examples/vyriy-browserslist-config/.