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

create-nectar-app

v0.1.1

Published

Scaffold a Nectar Dev Center app from the official templates.

Readme

create-nectar-app

Scaffold de um app do Nectar Dev Center a partir dos templates oficiais.

npm create nectar-app my-app
cd my-app
npx @nectarcrm/cli dev

Sem argumentos, o comando pergunta o nome do app e o template. Para pular o prompt:

npm create nectar-app my-app -- --template product-editor --yes

Templates

| id | O que gera | |---|---| | basic | Ponto de partida limpo: painel com status de conexão, eventos do CRM e um toast de exemplo. | | custom-module | Item no menu do CRM que abre uma página própria (dashboard standalone). | | product-editor | Painel no contexto de um produto: edita campos, valida no servidor e aplica estilo/badge em campos customizados. | | rest-starter | Base para integrar com qualquer API REST: painel de teste que dispara GET/POST via connector, com a chamada isolada numa function. | | contact-sync | Sincroniza contatos de um sistema externo para o CRM — por cron ou sob demanda, idempotente via mapeamento de IDs. |

O que ele cria

Além dos arquivos do template: nectar.config.json, .env.example (onde ficam as NECTAR_API_KEY_<ENV> — o .env real nunca é versionado), .gitignore e fixtures/ para o emulador offline.

No fim ele oferece configurar a publicação: pergunta o Dev Center, conduz o login (abre o browser) e então cria o app lá — ou vincula a um existente — emitindo a API key sozinho. Nenhum uuid ou chave para copiar. Dá para pular e rodar npx @nectarcrm/cli login depois.

O passo seguinte é o @nectarcrm/cli: nectar dev para o inner loop local, nectar deploy --env <env> para publicar.

Docs: https://developer.nectarcrm.com.br/docs/testing-locally · CLI: https://developer.nectarcrm.com.br/docs/cli