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

forte-lifecycle

v2.2.2

Published

An express middleware that automatically hooks in to forte perf and analytics

Downloads

25

Readme

forte-lifecycle Travis npm package

Forte Lifecycle is expressjs middleware that provides lifecycle magic to your Forte experience apps.

Features

  • Automatic Organization Resolver and Cache
    The first request processed will cause a forte-api call to be made that fills the organization cache. A request.organization prop will also be available for use in other areas of your express server.
  • Automatic server.renderTime metric tracking
    All requests are timed and logged via node-statsd

Install

$ npm i -S forte-lifecycle

Documentation

Quick Start

var express = require('express')
var forteApi = require('forte-api')
var lifecycle = require('forte-lifecycle')

var app = express()

var api = forteApi({...})

// register the middleware
// be sure to register the middleware before any routes that require trunk/branch scope info
app.use(lifecycle(api)) 

// now, all requests will have a request.lifecycle property
// and log server.renderTime using node-statsd
app.get('/', function (req, res) {
  res.send('Hello ' + req.lifecycle.scope.trunk '!');
});

app.listen(3000, function () {  
  console.log('Forte Experience app listening on port 3000!');
})

API

Constructor

ForteLifecycle(apiClient, [options])

Creates an instance of the Forte Lifecycle middleware.

  • apiClient:
    A forte-api client instance or an object that conforms to the following interface can also be supplied:
    • organizations.getOne(filter): {organization}
      Returns a promise that returns a single organization. filter is an object map of props to filter by e.x.: { hostname: '...'}.
    • organizations.getMany(filter): [{organization}, ...]
      Returns a promise that returns all organizations. filter is an object map of props to filter by e.x.: { parentID: '...'}.
  • options:
    • cacheDuration:
      The duration in milliseconds or string in ms format to cache organizations lookups.
      default: '15m'
    • stats:
      An optional configuration object for node-statsd.
      default: node-statsd defaults see node-statsd usage

Request Properties

The lifecycle middleware adds the following properties to the request for use in subsequent middleware/handlers:

request.lifecycle.scope: {object}

  • hostname: {string} The hostname of the request derived from request.headers.host.
  • trunk: {string}
    The trunk organization ID for the request.
  • branch: {string}
    The branch organization ID for the request.