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

@service-public-de-wallonie/string-utils-lib

v1.0.0

Published

A simple string utility library

Downloads

11

Readme

NodeJS Library Example

Exemple de librairie Node.js compatible avec le composant GitLab CI nodejs-component.

Prérequis

  • Node.js 20.18.x
  • npm

Installation

npm install

Scripts disponibles

| Commande | Description | | ---------------- | ----------------------------------------- | | npm run build | Compile la librairie (ESM + CJS + types) | | npm test | Exécute les tests avec couverture de code | | npm run lint | Analyse statique du code (ESLint) | | npm run format | Formate le code (Prettier) |

Structure du projet

├── src/                    # Code source
│   ├── index.ts           # Point d'entrée
│   ├── string-utils.ts    # Utilitaires de chaînes
│   └── text-utils.ts      # Utilitaires de texte
├── test/                   # Tests unitaires
│   ├── string-utils.test.ts
│   └── text-utils.test.ts
├── dist/                   # Build (généré)
│   ├── esm/               # Module ESM
│   ├── cjs/               # Module CommonJS
│   └── types/             # Déclarations TypeScript
└── reports/                # Rapports (généré)

Conventions pour GitLab CI

Répertoire des rapports

Tous les rapports doivent être générés dans reports/ :

| Fichier | Format | Usage | | -------------------------------- | --------- | -------------------------- | | reports/node-test.xunit.xml | JUnit | Résultats des tests GitLab | | reports/lcov.info | LCOV | Couverture SonarQube | | reports/cobertura-coverage.xml | Cobertura | Couverture GitLab MR |

Scripts obligatoires

Le composant GitLab CI exécute :

npm run build    # NODE_BUILD_ARGS
npm test         # NODE_TEST_ARGS (doit générer les rapports)
npm run lint     # NODE_LINT_ARGS

Configuration du coverage

Le script test utilise :

  • Test runner : node:test (natif Node.js)
  • Coverage : c8 avec reporters lcov, cobertura, text
  • Test reporter : spec (console) + junit (fichier)

Regex de couverture

Le composant CI extrait le pourcentage via :

/^All files\s*\|\s*(\d+(?:\.\d+)?)/

Le reporter text de c8 génère ce format automatiquement.