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

pepino

v1.0.59

Published

Pepino's app parses step files into UI automation instructions, sends those instructions to automation services, and reports results.

Downloads

3

Readme

Pepino

Pepino translates plain english UI steps from the Pepino Language into UI automation instructions, sends those instructions to automation services, and reports results.

Requirements

  • Node v4.4.7 (or newer)
  • NPM v2.15.8 (or newer)
  • Terminal or Console

Installation/Upgrade

You need to install the Pepino tool so that you can convert step files into js files.

  • npm install -g pepino

You also need to install Chimp to run the cucumber specifications with the converted js files.

  • npm install -g [email protected] (please don't use v0.39 because of a bug in cucumberjs 1.2.1)

Setup a project

Any project that will use Cucumber should have a folder called "features". Inside that folder, you should have all your cucumber-formatted specifications. Your Pepino step files should probably be in the same folder for easy access. Here's an example folder structure:

./
./src
./src/images
./features
./features/login
./features/login/authentication.feature
./features/login/authentication.step
./features/registration
./features/registration/first_time.feature
./features/registration/first_time.step

Use

While using the console, navigate to the root folder of your project. From there, you can run the following command to convert Pepino step files to javascript:

  • pepino

Once your Pepino step files have been converted, you can run Chimp to execute the specifications.

  • chimp

NOTE: Remember that, when you modify your Pepino step files, you need to convert them again before trying to execute them.

Samples

To help you get started, you can use the sample specifications and steps in the pepino-lib repository. Check the files in the ./test_assets/ folder. You can copy those files into your own ./features folder and get started immediately.