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

sendex

v0.3.4

Published

A lightweight API endpoint testing tool

Downloads

2

Readme

sendex

A lightweight API endpoint testing tool

Installation

Install globally with NPM:

npm install -g sendex

Usage

First you will need to initialize sendex in your project:

sendex init

This command will create the .sendex.yml file, which contains the global configuration sendex, and an empty set of sendex folders that are used to keep each request, response and test. The directory stucture is as follows:

  • requests: This will store the config files for each requests. A typical config file will contain the path, method and headers for that request.
  • responses: Responses from each request will be stored here.
  • tests: sendex gives you the ability to write JavaScript tests for each request, those tests go here.

To create your first request, use the following command:

sendex new get posts

This command is made up of three parts (excluding the sendex command). The new command specifies that we are creating a new request. The new command takes 2 arguments: the first argument is the method that we are using for the request, for this example we are using the GET method. The method can be written uppercase or lowercase. The next command is the path, relative to the URL. If we use posts like in the above example, the path that will be tested is /posts. If we wanted to send a request to the path /posts/all then we would use the command sendex new get posts/all for example.

sendex run get posts

To run that command, we can then use the same stucture, but with the run command instead.

You can also run tests on a request. Create a test in the tests folder and run it using (replacing with the file name of your test, excluding the file extension):

sendex test <TEST>

You can run all tests with:

sendex test

License

MIT