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

@saasquatch/scoped-autobindsteps

v1.0.1

Published

A replacement for jest-cucumber's autoBindSteps that doesn't use global scope.

Downloads

10

Readme

Scoped autoBindSteps for jest-cucumber

A replacement autoBindSteps function for use with jest-cucumber.

Currently, the jest-cucumber implementation of autoBindSteps stores all steps and feature files in the global scope. This can be a problem if you would like to use the same step names across different files but don't want them to conflict. This package solves that problem.

Each function call of autoBindSteps only binds the features and steps that you provide in that call.

Comparison

Here's a comparison between this implementation vs the original implementation of autoBindSteps

Original

This is what happens with autoBindSteps from jest-cucumber.

const allFeatures = loadFeatures(FEATURE_PATH + "*.feature");
const allSteps = [/* steps here */];

// all of the steps are bound to all of the features
autoBindSteps(allOfMyFeatures, allOfMySteps);

You might think that this keeps them separate, but it still mixes them together.

import {redSteps, blueSteps} from "./mySteps"

const redFeature = loadFeature(FEATURE_PATH + "Red.feature")
const blueFeature = loadFeature(FEATURE_PATH + "Blue.feature")

// this
autoBindSteps([redFeature], [redSteps])
autoBindSteps([blueFeature], [blueSteps])

// does the same thing as this
autoBindSteps([redFeature, blueFeature], [redSteps, blueSteps])

This way of doing things means that each step name must be unique. This becomes a problem when you have a large number of steps names, and as a result, the feature files can get quite verbose.

Scoped

This is what happens with autoBindSteps from this package.

import {redSteps, blueSteps} from "./mySteps"

const redFeature = loadFeature(FEATURE_PATH + "Red.feature")
const blueFeature = loadFeature(FEATURE_PATH + "Blue.feature")

// scopes are kept completely separate
autoBindSteps([redFeature], [redSteps])
autoBindSteps([blueFeature], [blueSteps])

Because of this, there can be steps in redSteps and blueSteps that have the exact same name and don't confict because they're only bound to one file.

This is nice because you can turn step names like this

press the red button in the yellow spaceship once

into step names like this

press the button once