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

@astroip-fr/presence-io

v1.0.0-rc41

Published

Presence IO - Desktop Application

Readme

jDeploy Configuration

Ce dossier contient la configuration jDeploy pour générer des installers natifs multi-plateformes de Presence IO.

🎯 Distribution Strategy

GitHub Releases uniquement - Aucun artefact n'est publié sur npm.

🔨 Build Local

Option 1: Build Maven uniquement

# Depuis la racine du projet
./scripts/jdeploy-build.sh

Produit: presence-desktop-app/target/presence-io-jdeploy.jar

Option 2: Build + Bundle jDeploy local

# Depuis la racine du projet
./scripts/jdeploy-bundle.sh

Produit:

  • JAR: presence-desktop-app/target/presence-io-jdeploy.jar
  • Bundle: jdeploy/jdeploy-bundle/

Option 3: Commandes manuelles

# Build Maven avec profil jDeploy
mvn -Pjdeploy -pl presence-desktop-app -am clean package -DskipTests

# Génération bundle jDeploy
cd jdeploy
npx jdeploy bundle

🚀 Publication (CI/CD)

La publication est automatisée via GitHub Actions:

Workflow: .github/workflows/jdeploy-release.yml
Déclencheur: Publication d'une GitHub Release

Process

  1. Build Maven avec profil -Pjdeploy
  2. Mise à jour de la version dans package.json
  3. Publication via npx jdeploy publish
  4. Installers créés pour la plateforme CI (Linux par défaut)

📦 Structure

jdeploy/
├── package.json          # Configuration jDeploy
├── .gitignore           # Exclusions build artifacts
├── README.md            # Ce fichier
└── jdeploy-bundle/      # (généré) Bundle jDeploy local

⚙️ Configuration

package.json

  • jdeploy.jar: Chemin vers le JAR stable produit par Maven
  • jdeploy.javaVersion: Version Java requise (17)
  • jdeploy.javafx: true (jDeploy télécharge JRE avec JavaFX)

Maven Profile

Le profil jdeploy dans presence-desktop-app/pom.xml:

  • Copie le JAR shaded existant (*-app.jar)
  • Vers un nom stable (presence-io-jdeploy.jar)
  • Zéro impact sur le build standard

🌐 Multi-Plateforme

Phase 1 (Actuelle): Linux uniquement

Le workflow CI tourne sur ubuntu-latest.

⚠️ Note JavaFX: Le POM utilise javafx.platform=mac-aarch64. Pour build CI Linux:

  • Option A: Utiliser macOS runner (runs-on: macos-latest)
  • Option B: Refactoriser JavaFX par profils OS

Phase 2 (Future): Matrix multi-OS

Pour générer des installers Windows/macOS natifs:

  1. Ajouter matrix strategy au workflow
  2. Adapter configuration jDeploy par OS
  3. Voir release.yml existant comme référence

📚 Documentation