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

@obsidiane/meridiane

v2.0.7

Published

Générateur de librairie Angular et modèles TypeScript (OpenAPI) pour un bridge Symfony/API Platform + Mercure.

Downloads

247

Readme

@obsidiane/meridiane

CLI pour générer un bridge Angular (runtime + models TypeScript) depuis une spec OpenAPI (API Platform + Mercure).

Documentation complète du repo : docs/guide-bridge.md.

Installation

npm i -D @obsidiane/meridiane

Commandes

meridiane generate <packageName>

Génère uniquement les sources du bridge dans le workspace courant.

npx meridiane generate @acme/backend-bridge --spec ./openapi.json

Sortie par défaut : projects/<libName>/ (modifiable via --out).

meridiane dev [packageName]

Génération + build standalone + npm pack + installation locale dans node_modules.

npx meridiane dev @acme/backend-bridge --spec http://localhost:8000/api/docs.json

Sorties :

  • dist/<libName>/ + dist/<libName>/*.tgz
  • node_modules/<packageName>/

meridiane build <packageName>

Génération + build standalone + npm pack (artefact publiable).

npx meridiane build @acme/backend-bridge --version 1.2.3 --spec https://staging.example/api/docs.json

Sorties :

  • dist/<libName>/
  • dist/<libName>/*.tgz

Options

  • --spec <url|file> : URL OpenAPI ou fichier JSON local (requis sauf --no-models)
  • --formats <mimeTypes> : répétable ou liste , ; défaut application/ld+json
  • --include <substr> / --exclude <substr> : filtres de noms de schémas (répétables, support ,)
  • --no-models : runtime only
  • --version <semver> : build et generate (défaut 0.0.0)
  • --out <dir> : uniquement generate
  • --debug : logs détaillés

Notes importantes

  • fallback automatique .../api/docs.json -> .../api/docs.jsonopenapi si nécessaire
  • mode contract-driven : uniquement les schémas atteignables via paths pour les formats sélectionnés
  • modèles *jsonMergePatch* non générés (PATCH typé Partial<T>)
  • Meridiane ne publie pas : publication via npm publish côté CI

Spécifique à ce repo

Dans ce monorepo, meridiane dev peut être exécuté sans packageName et cible alors @obsidiane/bridge-sandbox (app apps/sandbox).