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

@mostajs/logger

v0.1.0

Published

Primitive N0 de journalisation structurée : format canonique LogEntry (JSON-lines) + émetteur multi-driver (console/mémoire/flux). Consommé par @mostajs/audit (conformité) et @mostajs/qa-engine (QA). Statut : proposition (cas C).

Readme

@mostajs/logger

Auteur : Dr Hamid MADANI [email protected] · Licence : AGPL-3.0-or-later Niveau : N0 (primitif) · Statut : proposition (cas C — voir docs/00-CARTOGRAPHIE-ET-PROPOSITION.md)

Primitive de journalisation structurée de l'écosystème @mostajs/* : un format canonique LogEntry (JSON-lines) et un émetteur multi-driver. Le format vit ici (source unique) ; @mostajs/audit (conformité) et @mostajs/qa-engine (QA) le consomment.

Pourquoi pas dans @mostajs/audit ?

audit est un journal de conformité (qui/quoi/quand, RGPD) — un consommateur de logs, pas leur format généraliste. Fusionner violerait la responsabilité unique. logger (N0) est la couche basse partagée : logger ← audit, logger ← qa-engine (dépendance descendante).

Installation

npm i @mostajs/logger

Exemple minimal

import { createLogger, memoryDriver } from '@mostajs/logger';

const buf = memoryDriver();
const log = createLogger({ level: 'debug', drivers: [buf], base: { app: 'ticketflow' } });

log.info('Serveur démarré', { module: 'boot', event: 'server.started' });
log.child({ module: 'queue' }).error('Ticket introuvable', {
  requestId: 'r-142', error: { message: 'Ticket introuvable : MG1', code: 'E_NOT_FOUND' },
});

console.log(buf.entries.length); // 2

API

| Export | Rôle | |--------|------| | createLogger(config?) | crée un Logger (log/debug/info/warn/error/fatal/child) | | LogEntry, LogLevel | types du format canonique | | consoleDriver | driver console (stderr pour warn+) | | memoryDriver() | driver mémoire (.entries) — tests/buffer | | formatJsonl(entry) / parseJsonl(raw) | (dé)sérialisation JSON-lines |

config : { level?, drivers?, base?, now? } — now = horloge injectable (tests déterministes). DB-agnostique : la persistance est un driver fourni par le consommateur.

Statut

Proposition : squelette d'API stable + drivers de base. Suite (après validation) : livrables §9 (état de l'art logging structuré, audit, plan…) et refactor (extraire LogEntry de @mostajs/qa-engine vers ici ; audit adopte le format).