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

backender

v0.0.7

Published

gulp plugin to test and mock back-end server

Downloads

2

Readme

backender

backender

STEP 1. Get backender : To get started you need to pull down backender from npm. This will enable you set up a back-end api

npm install backender

STEP 2 (OPTIONAL). Get testbuilder To setup the environment so that you can add steps and tests, pull down backender-testbuilder from npm

npm i backender-testbuilder

STEP 3. Provide settings : Now the last step is to create a settings.json file with details of how you want the api endpoint to behave

The simplest settings.json file content looks like this

{

"config": [{

"apiport": 8891

}] }

See Wiki [ https://github.com/getbackender/backender/wiki ] for more information

chrome driver for testing

http://chromedriver.storage.googleapis.com/index.html