
Security News
curl Shuts Down Bug Bounty Program After Flood of AI Slop Reports
A surge of AI-generated vulnerability reports has pushed open source maintainers to rethink bug bounties and tighten security disclosure processes.
@saasquatch/scoped-autobindsteps
Advanced tools
A replacement for jest-cucumber's autoBindSteps that doesn't use global scope.
autoBindSteps for jest-cucumberA 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.
Here's a comparison between this implementation vs the original implementation of autoBindSteps
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.
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
FAQs
A replacement for jest-cucumber's autoBindSteps that doesn't use global scope.
We found that @saasquatch/scoped-autobindsteps demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 11 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
A surge of AI-generated vulnerability reports has pushed open source maintainers to rethink bug bounties and tighten security disclosure processes.

Product
Scan results now load faster and remain consistent over time, with stable URLs and on-demand rescans for fresh security data.

Product
Socket's new Alert Details page is designed to surface more context, with a clearer layout, reachability dependency chains, and structured review.