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

@hexapack/native-cli

v0.1.0

Published

CLI and SDK for creating, validating, packaging, and signing HEXA Native extensions.

Readme

HEXA Native CLI/SDK

CLI separado para developers criarem, validarem, empacotarem e assinarem extensoes HEXA Native sem clonar o projeto inteiro do HEXA Browser.

Instalar

Quando o pacote estiver publicado:

npx @hexapack/native-cli --help

O pacote oficial usa o escopo npm @hexapack porque o escopo @hexa nao esta disponivel para esta organizacao. O binario instalado continua sendo hexa-native.

Enquanto o pacote ainda estiver dentro deste repositorio:

node packages/hexa-native-cli/bin/hexa-native.mjs --help

Gerar chave do developer

Rode no computador do developer, nunca no servidor aaPanel/Docker:

npx @hexapack/native-cli keygen \
  --out-dir ~/.hexa/native/keys \
  --name hexa-publisher

O comando cria:

  • ~/.hexa/native/keys/hexa-publisher-private.pem: fica somente com o developer.
  • ~/.hexa/native/keys/hexa-publisher-public.pem: cola no Developer Portal, em Store > Publisher.

Criar starter

npx @hexapack/native-cli init ./minha-primeira-extensao-hexa \
  --name "Minha Primeira Extensao HEXA" \
  --slug minha-primeira-extensao-hexa \
  --publisher-public-key ~/.hexa/native/keys/hexa-publisher-public.pem

Validar antes do upload

npx @hexapack/native-cli validate \
  --source ./minha-primeira-extensao-hexa \
  --private-key ~/.hexa/native/keys/hexa-publisher-private.pem

Empacotar e assinar

npx @hexapack/native-cli package \
  --source ./minha-primeira-extensao-hexa \
  --out ./dist/minha-primeira-extensao-hexa.hexa \
  --private-key ~/.hexa/native/keys/hexa-publisher-private.pem

O upload no Developer Portal recebe:

  • o arquivo .hexa;
  • o conteudo do arquivo .hexa.sig no campo Assinatura destacada;
  • o mesmo Publisher/public key usado no manifest.

API SDK

import { keygen, initExtension, validateExtension, packageExtension } from '@hexapack/native-cli';

Essas funcoes permitem criar uma interface grafica, CI ou futuro Developer SDK sem depender do Browser.

Publicacao no npm

O guia de release do pacote esta em docs/hexa-native-cli-npm-publish.md.

Resumo para maintainers:

cd packages/hexa-native-cli
npm pack --dry-run
npm publish --access public