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

@portaki/module-sdk

v1.2.0

Published

Portaki module SDK — guest UI, schema, gateway handlers (build with @portaki/module-cli)

Readme


Installation

npm install @portaki/module-sdk react
# ou
pnpm add @portaki/module-sdk react

Peer : react ≥ 18.


Démarrage rapide

Expose un export default depuis le point d’entrée de ton paquet npm (comme les modules @portaki/module-* du monorepo) :

import { definePortakiModule } from "@portaki/module-sdk";

export default definePortakiModule({
  id: "hello",
  label: { fr: "Bonjour", en: "Hello" },
  icon: "sparkles",
  navSlot: "section",
  render: ({ property, stay, lang }) => (
    <section style={{ padding: "1rem" }}>
      <h2>{lang === "fr" ? "Votre séjour" : "Your stay"}</h2>
      <p>{property.name}</p>
    </section>
  ),
});

definePortakiModule complète les champs optionnels (description, version, navSlot, …) avec des valeurs par défaut cohérentes pour le runtime Portaki.


API publique

| Export | Rôle | |--------|------| | definePortakiModule | Fabrique une définition de module typée (PortakiModuleDefinition). | | useTracking | Hook optionnel pour instrumentation / analytics côté module. | | Composants | ModuleSection, ModuleCard, ModuleLoading, ModuleError, ModuleEmpty, CopyButton, ExternalLink, WazeButton, GoogleMapsButton, ModuleConfigAlert — blocs UI alignés sur la page invité. | | Types | ModuleContext, StayData, PropertyData, NavSlot, StayStatus, schéma de config module (ModuleConfigSchema), etc. |

Manifest JSON des modules : schéma module.v1 dans le dépôt portaki-sdk (schema/module.v1.json). Le champ requiresHostSdk (semver X.Y.Z) indique la version minimale de @portaki/module-sdk avec laquelle le module a été validé — aligner sur la version publiée du paquet npm (sdk/module-sdk/package.json).


Liens

| Ressource | URL | |-----------|-----| | Site & marque | portaki.app | | Monorepo (Java, modules, CI) | github.com/PortakiApp/portaki-sdk | | Paquet npm | npmjs.com/package/@portaki/module-sdk | | Guide développeur | Getting started | | SDK Java (Maven) | sdk/java |


Build local

cd sdk/module-sdk
npm ci
npm run build

Les types et le JS compilé sortent dans dist/.


Version Java (Maven)

Backend des modules : artefact app.portaki:portaki-module-sdkREADME Java.


Licence

MIT — voir le champ license du package.json.