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

@horizon-integrations/jetimob-crm-client

v1.0.1

Published

Client HTTP tipado pra consumir a API do horizon-integrations-hub (rotas /api/providers/jetimob/v1/*). Instalado nos sites das imobiliárias pra puxar imóveis via hub, preservando Anti-Corruption Layer.

Readme

@horizon-integrations/jetimob-crm-client

Client HTTP tipado pra consumir o horizon-integrations-hub (rotas /api/providers/jetimob/v1/*). Instalado nos sites das imobiliárias, dentro de apps/automations/.

Preserva o Anti-Corruption Layer: o site nunca chama a API Jetimob direto — sempre vai pelo hub, que orquestra.

Site (JetimobClient) → HTTP → Hub (jetimob-crm) → HTTP → API Jetimob

Instalação

pnpm add @horizon-integrations/jetimob-crm-client

Config

import { JetimobClient } from "@horizon-integrations/jetimob-crm-client"

const jetimob = new JetimobClient({
  baseUrl: process.env.HUB_URL!,            // https://horizon-integrations.vercel.app
  authToken: process.env.HUB_API_KEY!,      // x-api-key do hub
  tenantCredentials: {
    webserviceKey: process.env.JETIMOB_WEBSERVICE_KEY!,
  },
})

Uso — runSync (o padrão das automations dos sites)

É assim que cada site sincroniza, dentro de uma Inngest function sync-properties-jetimob.ts (ver examples/sync-properties-jetimob.ts):

import { JetimobClient } from "@horizon-integrations/jetimob-crm-client"
import { HttpDestination, runSync } from "@horizon-js/integrations-core/destinations"
import { DestinationSyncMode } from "@horizon-js/integrations-core"

const source = new JetimobClient({
  baseUrl: process.env.HUB_URL!,
  authToken: process.env.HUB_API_KEY!,
  tenantCredentials: { webserviceKey: process.env.JETIMOB_WEBSERVICE_KEY! },
}).properties

const destination = new HttpDestination({
  endpoint: `${process.env.NEXT_PUBLIC_API_URL}/api/property/sync`,
  apiKey: process.env.API_SECRET_KEY!,
  sourceKey: "jetimob-api-imoveis",
})

const result = await runSync({
  stream: source,
  destination,
  mode: DestinationSyncMode.APPEND_DEDUP,
})
// result: { recordsRead, recordsCreated, recordsUpdated, recordsDeleted, errors, ... }

runSync lê via source.streamAll(), faz delta por sync_hash e dá upsert só do que mudou no destino.

API

JetimobClient

| Membro | Descrição | |---|---| | properties | PropertiesResource — o resource de imóveis | | capabilities | Espelho das capabilities do runtime | | check() | Valida credenciais + conectividade com o hub |

JetimobClient.properties (PropertiesResource)

| Método | Rota do hub | Descrição | |---|---|---| | fetchAll<T>() | POST /properties | Dump completo { properties, errors, total } | | getListing() | POST /properties/index | Lista leve { index, total }ref=id_imovel, updatedAt=null | | get<T>(ref) | POST /properties/[ref] | Um imóvel ou null (404). Aceita id_imovel ou codigo | | streamAll<T>() | — | AsyncGenerator que runSync consome | | check() | — | Valida credenciais |

Uso direto (sem runSync)

// Seed inicial
for await (const p of jetimob.properties.streamAll()) {
  await db.properties.upsert(p)
}

// Pontual
const one = await jetimob.properties.get("6570922")

// Detecção de deletados
const { index } = await jetimob.properties.getListing()
const idsAtivos = new Set(index.map((e) => e.ref))

Ver examples/ e a doc end-to-end em Integrações/docs/INTEGRATION-LIFECYCLE.md.