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

sails-hook-recap-dev

v1.0.1

Published

Sails.js hook Recap.Dev, an open-source cloud observability and tracing solution for modern JavaScript backends.

Downloads

2

Readme

npm downloads GitHub license recap.dev Docker Hub

Website | Documentation | Demo | Report a Bug

recap.dev is an open-source cloud observability and tracing solution for modern JavaScript backends. Our goal is to make it easier for everyone to find sources of errors, find bottlenecks, and improve overall developer quality of life.

  • Detailed per-endpoint tracing: recap.dev builds a timeline of what is going on during endpoint handler execution. That includes database and external calls as well as timings of individual functions simplifying debugging and performance optimization. recap.dev also provides an overview of the system and tries to give you as much useful information as possible.

  • Easy-to-setup: recap.dev server is easy to start with a couple of commands. It is shipped as a Docker container, so it can be started wherever you host your applications. We try to integrate with as many tools as possible to provide an easy way of tracing your application with minimal to no code changes.

  • Open-source: We believe that development tools should be open-source. Especially tools that might gather or contain sensitive data. Hosting these tools on your servers is important so that the sensitive data never leaves your organization. It is also important to know what precisely these tools do with your data.

Learn how to start with recap.dev

sails-hook-recap-dev

sails-hook-recap-dev repository contains source-code for a Sails.js tracing hook.

Usage

  1. Install the Hook
yarn add sails-hook-recap.dev

or

npm i --save sails-hook-recap.dev
  1. Configure Sync Endpoint

In your config/env/production.js or other environments you'd like to trace your application on, add the following:

  'recap-dev': {
    syncEndpoint: 'https://tracing.recap.dev/traces'
  },

Read the official Sails.js documentation on the hooks configuration here

Available configuration options:

  • syncEndpoint - Required, points to your Recap.Dev installation tracing endpoint.
  • filterRequest - Optional, function that accepts a request and returns true to trace the request or false to ignore it. Useful to ignore requests to assets. Default is:
filterRequest: (request) => request.originalUrl.startsWith('/api/')
  • disableAutomaticUnitNames - Optional, if set to true no unit names will be created automatically. Note that you will need to call tracer.setUnitName to provide a unit name, otherwise it will be set as a current hostname.

Learn how to use this library to trace your application with recap.dev