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

telepat-api

v0.4.4

Published

This is the Telepat API where all api calls are made. CRUD operations are not processed here directly. Messages are sent to the Telepat workers where CRUD operations are being taken care of along with client communication (notifications)

Downloads

17

Readme

Telepat API

This is the Telepat API where all api calls are made. CRUD operations are not processed here directly. Messages are sent to the Telepat workers where CRUD operations are being taken care of along with client communication (notifications)

Quick startup guide

To start the API server all you need to do is run one command:

./bin/www

You can optionally tell the server to listen another port (default is 3000) by setting the environment variable PORT. The API server will try and connect to each of the services until they are available (kafka, couchbase, elasticsearch).

Configuring

There are two ways to configure: either by using the config.example.json config file (rename it into config.json) or by setting up environment variables (this method is the most convenient):

  • TP_MSG_QUE: Name of the messaging client you want to use. Should be the same as the exported variable in telepat-models
  • TP_MAIN_DB: Name of the main database which to use. Should be the same as the exported variable in telepat-models
  • TP_PW_SALT: Password salt used for hashing passwords

Important: You need to set up the other config variables specified in the telepat-models README file for resources that you're using.

Testing

To run just the tests using mocha (make sure you have installed globally npm install mocha):

  • mocha api.js in the test folder
  • npm test in the root folder will also run istanbul (make sure you install it globally) code coverage tool

Notice: the testing suite automatically starts the API server but NOT the telepat workers. You should start them before running the tests.

API documentation can be found here: http://docs.telepat.io/api-docs.html