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

@creezio/os-ui

v0.26.1

Published

Surfaces Next OS natives (mails, tasks, setup, admin…) — matérialisées hors git dans les marques

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

cedfiduciacedfiducia

Keywords

Readme

@creezio/os-ui

Rôle

@creezio/os-ui contient les surfaces Next de l'OS (pages non métier) : mails, tâches, setup, login, onboarding, MCP, cockpit/server-cockpit, paramètres, admin (analytics, database, plugins, request-logs)… Ces pages ne vivent pas dans le repo marque : elles sont matérialisées dans l'app Next de la marque au build, dans le groupe App Router (creezio-os) (gitignoré côté marque).

Contenu

| Zone | Contenu | |------|---------| | routes/ | Pages Next OS (wrappers minces sur @creezio/<pkg>/ui) — dont /admin/nav | | src/index.ts | OS_UI_ROUTE_SEGMENTS, OS_PRIMARY_NAV_SEGMENTS, OS_UI_HORS_NAV_JUSTIFICATIONS, OS_UI_ROUTE_GROUP, export CreezioUiBoot | | src/boot.tsx | CreezioUiBoot — boot client OS (identité desktop + tokens shell-ui + InteractiveDemoRoot natif) | | scripts/materialize.mjs | CLI creezio-materialize-os-ui — copie routes/ → ui/app/(creezio-os)/ de la marque |

Usage côté marque

# copie les pages OS dans l'app Next de la marque (dossier gitignoré)
creezio-materialize-os-ui --app-root <brandRoot>
# ou : node node_modules/@creezio/os-ui/scripts/materialize.mjs --app-root .

Le layout racine de la marque enveloppe l'app avec CreezioUiBoot (import @creezio/os-ui/boot) :

<CreezioUiBoot desktopApiGlobal="maMarqueDesktop" productName="Ma Marque"
  publicHostSuffix=".mamarque.example">
  {children}
</CreezioUiBoot>

Règles

  • La marque ne réécrit jamais une page OS : elle rematérialise. Les segments OS_UI_ROUTE_SEGMENTS sont interdits dans le ui/app versionné d'une marque (gates kit).
  • Une page OS de ce package est un wrapper mince : la logique vit dans le package plateforme correspondant (@creezio/mails/ui, @creezio/tasks/ui, @creezio/onboarding/ui, @creezio/nav/ui, …).

Liens