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

@imolko/ultra-reporter

v1.0.17

Published

Reporter and documentation for: domain, use-cases and tests

Downloads

1,186

Readme

Como usar ultra-reporter

  1. Instale el paquete @imolko/ultra-reporter en su ultima version:
npm install @imolko/ultra-reporter
  1. Agregue la siguiente configuracion al jest en su archivo jest.config.js:

module.exports = {
  ...
  reporters: [
    "default",
    [
      "jest-html-reporters",
      {
        publicPath: "./html-report",
        filename: "journal.html",
        openReport: true,
        pageTitle: "Journal report",
      },
    ],
    [
      "./ultra-reporter-workspace/generate-domain-documentation.js",
      {
        contextName: "my-context",
      },
    ],
  ],
  ...
};

Nota: El valor de contextName debe ser el nombre del contexto que se esta documentando.

  1. Corra el comando para crear/actualizar los archivos relacionados con la documentacion:
npx @imolko/ultra-reporter
  1. Corra los test de jest:
npm run test

ó

npx jest
  1. Estando dentro de la carpeta documentation instale las dependencias:
npm install
  1. Corra el servidor de documentacion:
npm run start

Consideraciones

  1. La documentacion relacionada al contexto debe estar en un archivo llamado context-intro.md en la carpeta src.

  2. Este paquete asume que la estructura de los archivos en la capeta src hace uso del paquete @imolko/ultra-ddd y por tanto tiene una estructura como la siguiente:

src
├── domain
│   ├── Artifact1
│   │   ├── attachments.md
│   │   ├── conditions.ts
│   │   ├── definition.ts
│   │   ├── definition.yaml
│   │   ├── entity.spec.ts
│   │   ├── entity.ts
│   │   ├── index.ts
│   │   ├── payload.ts
│   │   ├── primitive.ts
│   │   ├── props.ts
│   └── Artifact2
│   │   ├── ...
├── features
│   ├── Feature1
│   └── Feature2
└── context-intro.md

Los archivos attachments.md y definition.yaml contiene parte importante de la documentacion de los artefactos, por lo que es importante que esten presentes en la estructura de los archivos y este bien documentados.

  1. En la carpeta documentation se generan los archivos relacionados con la documentacion de los artefactos y una introducccion al contexto.

  2. Dentro de documentation no se pueden realizar cambios a los archivos generados:

  • documentation/docs/aggragate/*
  • documentation/docs/domain/*
  • documentation/docs/intro.md
  1. Dentro de documentation hay archivos que deben ser editados para ajustarlos a cada contexto, como:
  • /documentation/docusaurus.config.ts
  1. Dentro de documentation se pueden generar paginas y blogs para documentar de forma manual otros aspectos del contexto. Vea Docusaurus