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

dt-jest

v0.0.44

Published

Este paquete reúne las configuraciones estándar utilizadas en los Test Unitarios y también permite que otros proyectos lo adopten como base para extender sus propias configuraciones.

Readme

Test Config

Este paquete reúne las configuraciones estándar utilizadas en los Test Unitarios y también permite que otros proyectos lo adopten como base para extender sus propias configuraciones.

Instalación

npm install --save-dev @types/jest jest jest-environment-jsdom jest-environment-node ts-jest
npm install --save-dev @delgadotrueba/react-config

Uso

Configuración de los test

La aplicación utiliza la biblioteca Jest para ejecutar los test unitarios. Cada componente cuenta con su propio archivo _.test.tsx o _.test.ts, donde se definen las pruebas específicas de ese componente. Al ejecutar los tests, se analiza el código de todos los componentes, generando métricas de cobertura que luego se consolidan en un único reporte.

Configuración de Jest

Para utilizar la configuración, se debe extender la configuración de @delgadotrueba/react-config/jest-preset en el fichero jest.config.js:

const { pathsToModuleNameMapper } = require("ts-jest");
const { compilerOptions } = require("./tsconfig.paths.json");

/** @type {import('ts-jest').JestConfigWithTsJest} */
module.exports = {
  displayName: 'my-app',
  preset: "@delgadotrueba/react-config/jest-preset",
  setupFilesAfterEnv: ["<rootDir>/src/utils-test/setupTest.ts"],
  transform: {
    "^.+\\.[tj]sx?$": ["ts-jest", { tsconfig: "<rootDir>/tsconfig.spec.json" }],
  },
  moduleNameMapper: {
    ...pathsToModuleNameMapper(compilerOptions.paths, { prefix: "<rootDir>/" }),
  },
    collectCoverageFrom: [
      'src/**/*.{js,jsx,ts,tsx}',
      'src/*.{js,jsx,ts,tsx}',
      '!src/**/*.stories.{js,jsx,ts,tsx}',
      '!src/**/*.examples.{js,jsx,ts,tsx}'
    ]
};

Funciones utilitarias

Además, el paquete incluye funciones utilitarias que simplifican la escritura y mantenimiento de los tests.

TODO

customRender

Función que permite renderizar un componente con el ThemeProvider y otros providers que se necesiten. Es un wrapper sobre la función render de @testing-library/react. (https://testing-library.com/docs/react-testing-library/setup#custom-render)

import { customRender } from "@delgadotrueba/react-config/jest-preset/src/test-utils";

describe("MyComponent", () => {
  it("should render", () => {
    const { container } = customRender(<MyComponent />);
    expect(container).toBeInTheDocument();
  });
});