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

evalserver

v0.1.0

Published

A mocking server for REST endpoints with templating abilities

Downloads

2

Readme

Evalserver

Eval server is a REST mocking tool that allows templating and changing of states.

Starting

You can start the server as follows

const { startServer } = require("./index")

startServer(9000, "./mock/", "mock", "status");

| startServer | | | ---------- | ------------- | | port | The port to host the mocking server on | | mockFolder | The folder to look in for mocks | | mockPrefix | A prefix url to the mock, i.e localhost:port/prefix will point to root | | statusPrefix | A prefix url to get to the status pages |

Structure

Each endpoint should be located in a separate folder under you mock folder.

The folder should contain a get.json with a template to be returned.

The template can contain {{variables}} that will be matched to a state found in state.js which should do a "normal" module.exports of its state.

Example

mock/asd/get.json:

{
    "param": "hello {{data}}!"
}

mock/asd/state.js:

module.exports = {
    data: "world"
}

HTTP GET http://localhost:9000/mock/asd/

{
    "param": "hello world!"
}

HTTP GET http://localhost:9000/status/asd/

{
  "hits": 1
}