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

@codeparrot/js-agent

v2.0.4

Published

Record and replay API traffic

Downloads

465

Readme

What is CodeParrot?

Get a change report on response body, latency & error rates of your APIs!

Example Diff

An Example Diff

CodeParrot uses AI and production traffic to generate a change report. This report gives you insights on differences in response body for all unique requests coming to your service!

It works by "recording" production (or staging env) traffic. Our AI figures out the unique API calls from this traffic, and also mocks the downstream dependencies! Magic right?! 🤯

Then for every PR, the above unique API calls are run against the new version of code. Its like- auto-generated functional tests (API calls for a service, with dependencies mocked).

Installation

Step 1 - Install the nodeJs "record" agent

  1. Install the CodeParrot dependency @codeparrot/js-agent by running

    npm install @codeparrot/js-agent

    This will add a dependency "@codeparrot/js-agent": "^1.2.3", in your package.json

  2. Update the node start app command with -r @codeparrot/js-agent, like

    "scripts": {
        "server": "node -r @codeparrot/js-agent index.js"
    }

This basically require’s the code parrot agent package before your application code.

Set the following env variable:

# set it to your *unique* service name
CODE_PARROT_APP_NAME=<service-name>

When you start your nodeJS application and see a log line like:

@codeparrot/js-agent, v1.2.5 nodejs-agent-<...>gserviceaccount.com

CodeParrot record is set up! 🎉 Use your application as normal, and CodeParrot will record the network traffic.

Step 2 - Install GitHub App

Install the CodeParrot GitHub App in the repo(s) that already have replay set up. (It asks for the minimum possible permissions)

Then, create 2 new files:

  1. codeparrot-replay.Dockerfile
  2. codeparrot.sh

to run the tests. Every code push, this Dockerfile is built and run. This new Dockerfile is almost as same as your existing one, except that it sets the CMD to run codeparrot.sh instead of the usual npm start.

codeparrot.sh runs your app start command (like npm start) in a loop, until all the tests execute.

Example codeparrot.sh :

#!/bin/sh

while :
do
    CODE_PARROT_IS_REPLAY=true npm start && break
    echo "Non-zero exit! Restarting replay..."
done

Example codeparrot-replay.Dockerfile :

# ... existing app setup

COPY codeparrot.sh ./codeparrot.sh

CMD ["sh", "./codeparrot.sh"]

Now, in every PR, a GitHub "check" with a link to the Change Report will appear: 🎉

GitHub Check

Contributing, Self Setup

Refer to CONTRIBUTING.md