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

newrelicbuster

v1.0.4

Published

A monkey patch to enable New Relic to run on Kraken applications.

Downloads

6

Readme

#NewRelic Buster A monkey patch to allow New Relic to run on Kraken Apps without messing up the routing.

##The problem New Relic is like the facehuggers from alien. Once it grabs a hold of your code, it don't let go.

FaceHugger

In order to instrument an Express app, it needs to inject itself into all middleware stacks, after middleware, and before error handlers. To do this, it patches several methods in express, allowing it to hijack calls that modify the middleware stack.

In our particular case, we're focusing on Routing. Routes in express are treated as middleware, so, NewRelic tries to get in on the action. Because it needs to be as close to the end of the stack as possible, whenever a new route is added, it will remove the interceptor from the stack, add the new route, and then add the interceptor after it.

The problem lies in the removal step.

To remove they use Array.filter. node_modules/newrelic/lib/instrumentation/express.js:404 (Ironic Line number is Ironic...)


// Remove our custom error handler.

         app.stack = app.stack.filter(function cb_filter(m) {
         if(m === interceptor){
         console.log();
         }
         return m !== interceptor}.bind(app))

Pretty elegant. However, Array.filter returns a new Array. This kills some in-memory references that Kraken uses to maintain it's route stack.

This patch works it's way down NewRelic's code to modify the above function to use Array.splice instead, using the same clever tricks as NewRelic.

 
         var i = app.stack.length -1;
         for (; i>=0; i--){
             if(app.stack[i]===interceptor) {
                 app.stack.splice(i,1);
             }
         }

##Usage Simply require this before newrelic gets loaded


'use strict';
require('newrelicbuster')
require('newrelic');
var http = require('http');
var express = require('express');
var kraken = require('kraken-js');

##Caveat Emptor

Hey, this is just a Sunday afternoon patch! Feel free to contribute as you see fit, but in reality you should go bother New Relic to fix their code.

Not an official Kraken / PayPal / New Relic project.

Go say hello on the birdsphere