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

@nerdvision/agent

v2.0.4

Published

The official node agent for NerdVision

Downloads

11

Readme

https://nerd.vision node agent

This is the official nerd.vision node agent. We're constantly looking to improve, so please send us feedback on it's usability and if you find any issues! You can see the known issues at the bottom of this readme.

Requirements

  • Node 10+

Documentation

You can find the documentation at docs.nerd.vision

Installation

npm i @nerdvision/agent

Configuration Properties

All configuration properties are defined in NerdVisionConfig

interface NerdVisionConfig {
	api_key: string;
	name?: string; // default: my-node-app
	debug?: boolean; // default: false
	tags?: { [key: string]: string }; // default: {}
}
⚠ Breaking change in v1.0.0: ️apiKey has been renamed to api_key

Usage

Both init and wrap accept an API key, or the configuration object. The example below is typescript, but nerd.vision works perfectly with normal javascript as well.

const {nerdvision, NerdVisionConfig} = require('@nerdvision/agent');

const config: NerdVisionConfig = {
	api_key: 'API_KEY', // you can find yours at https://account.nerd.vision/account/apikeys
};

//
// THEN
//

nerdvision.init('API_KEY').then(() => {
	// application code
});

//
// OR
//

nerdvision.init(config).then(() => {
	// application code
});

When Node exits, nerd.vision should automatically disconnect. If you want to ensure that it has disconnected, you can explicitly call close in your shutdown handler:

nerdvision.close();

You can also use .wrap to automatically disconnect after your code has run. This is more useful for applications that shut down after processing.

nerdvision.wrap(config, async () => {
	// application code
	
	// this function must return a promise
	// when it resolves, nerd.vision will disconnect automatically
});

Examples

There are two example node applications for nerd.vision.

Troubleshooting

I get the error TS7016: Could not find a declaration file for module 'google-protobuf'

  • You need to install types for google-protobuf: npm i -D @types/google-protobuf

I get errors when i use import on nerd.vision

  • Please use the require syntax above for now, we're actively looking into fixing this

Known issues

  • When using a pre-processor for JavaScript, like TypeScript, files that are lazy loaded may not trigger until they are run for a second time.
  • ts-node is not supported yet. As a work around, you can build your code with tsc and run it directly with node for tracepoints to fire