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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@brocan/bond

v3.0.2

Published

The build agent of Brocan CI.

Downloads

13

Readme

Bond

Bond is the build agent of Brocan CI.

Project Dependencies

  • brocanfile

Environment Dependencies

  • Faktory
  • NATS (Hemera)
  • Git must be installed in the container/machine running Bond

Expected configuration and environment variables

Please see the schema in src/config.js for documentation and default values.

Communication

Inbound

TCP

Faktory
  • Description: Uses Faktory for fetching new build jobs.

HTTP

POST /:buildId/report/:stage
  • Request
    • URI Params
      • buildId - The ID of the currently executing build. An arbitrary string.
      • stage - The build stage the report belongs belongs to. Can be any of these three values: command, step, build.
    • Payload
      • Please refer to the outbound communication of Bolt.
  • Response
    • Immediate with empty payload and 200 OK status code.
  • Description
    • This is the endpoint Bolt is intended to use when reporting the build status.

Outbound

NATS - Act

Build progress update
  • Topic - build.info
  • Type - pub/sub
  • Payload
    • role - progress
    • buildId - The identifier of the build.
    • stage - The stage the update, which can be build, step or command.
    • And all the same fields as those received on the /:buildId/report/:stage/ endpoint.
  • Description
    • An asynchronous build progress update.
Build data fetch
  • Topic - build.queryBuildData
  • Type - req/repl
  • Payload
    • buildId - The ID of the requested build metadata.
  • Description
    • Query data for specific build. The data must include the information needed for the build execution. This includes the repository URI and the commit hash.