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

segio

v1.0.1

Published

Segment api cli

Downloads

5

Readme

CLI for sending events to segment.com Sometime you need to replay events, trigger traits on a list of users. This tool is great for that.

Install

npm install -g segio

It requires that you have your SEGMENT_WRITE_KEY as an environment variable when this command is run.

Identify

Trigger Idenify via text user list

Assume users.txt:

pam
jim
michael
cat users.txt | segio identify --traits '{"office": "scranton", "status": "employed"}'
analytics.identify({
  userId: 'pam', // stdin
  traits: {
    office: "scranton",
    status: "employed"
  }
});

Trigger Identify via json user / traits list

You can use line delimited json, in the same format as the docs expect

Assume users.json:

{"userId": "pam", "traits":{ "job": "office manager", "status": "employed"}}
{"userId": "jim", "traits":{ "job": "sales", "status": "employed"}}
{"userId": "michael","traits":{ "job": "manager", "status": "retired"}}
{"userId": "ryan", "traits":{ "job": "sales", "status": "fired"}}
cat users.json | segio identify -f json
analytics.identify({
  userId: 'pam', // parsed json stdin.
  traits: {
    office: "scranton"
  }
});

Track

Trigger track via text user list

Assume users.txt:

pam
jim
michael
cat users.txt | segio track --event 'Pranked Dwight' --properties '{"prank": "stapler in jello"}'

Is the equivalent of this call on each of the users piped in via stdin. --properties is optional

analytics.track({
  userId: 'pam', // username form stdin
  event: 'Pranked Dwight',
  properties: {'prank': 'stapler in jello'},
});

Trigger track via json list

You can use line delimited JSON, in the same format as the docs expect

Assume users.json:

{"userId": "pam", "event": "Pranked Dwight" "properties":{ "prank": "stapler in jello"}}
{"userId": "jim", "event": "Pranked Dwight" "properties":{ "prank": "fax from future"}}
{"userId": "michael", "event": "Pranked Dwight" "properties":{ "prank": "friendship"}}
cat users.json | segio track -f json
analytics.track({
  userId: 'pam', // username form stdin
  event: 'Pranked Dwight',
  properties: {'prank': 'stapler in jello'},
});

debug

To enable debugging segio --debug

This will print when request to segment complete.