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

barso

v0.6.1

Published

Configurações compartilhadas para projetos JS/TS

Readme

Barso: Configurações e CLI

Configure um ambiente de desenvolvimento e testes com configurações similares às utilizadas no TabNews, incluindo:

Instalação

Para adicionar ao projeto, execute o comando:

npm i -D barso

Para utilizar a CLI, instale globalmente com o comando:

npm i -g barso

Configuração

No diretório raiz do projeto, adicione os respectivos arquivos de configuração de cada ferramenta utilizando as exportações da biblioteca barso.

ESLint (eslint.config.js)

export { default } from 'barso/eslint';

ou

const defaultConfig = require('barso/eslint');

const config = [
  ...defaultConfig,
  {
    // configurações adicionais ou sobrescritas
  },
];

module.exports = config;

lint-staged (lint-staged.config.js)

export { npm as default } from 'barso/lint-staged';
// export { pnpm as default } from 'barso/lint-staged';
// export { yarn as default } from 'barso/lint-staged';

Prettier (prettier.config.js)

export { default } from 'barso/prettier';

Vitest (vitest.config.js)

import defineConfig from 'barso/vitest';

const config = defineConfig({
  test: {
    // configurações adicionais ou sobrescritas
  },
});

export default config;

Utilização

Adicione scripts no package.json do projeto, por exemplo:

{
  "scripts": {
    "test": "barso test run",
    "test:watch": "barso test",
    "lint": "eslint . && prettier --check .",
    "lint:fix": "eslint --fix . && prettier --write .",
    "prepare": "husky",
    "pre-commit": "lint-staged"
  }
}

@tabnews/config

Até a versão 0.6.0, este repositório também foi a casa da biblioteca @tabnews/config, que fornecia configurações padronizadas para os repositórios do TabNews. A partir desta versão, a biblioteca foi renomeada e publicada no NPM como barso.

Para facilitar a migração, as versões @tabnews/[email protected] e [email protected] são idênticas, mas podem divergir em futuras versões.

O desenvolvimento da biblioteca @tabnews/config, caso mantido, irá ocorrer no repositório filipedeschamps/tabnews-config.