@oselvar/var

The package you write step definitions against. Import steps, give it a factory for your scenario state (and optionally custom parameter types), and use the returned stimulus / sensor functions to bind Cucumber-expression steps.

import { steps } from '@oselvar/var'

const { stimulus, sensor } = steps(() => ({ greeting: '' }))
stimulus('I greet {string}', (_state, name) => ({ greeting: `Hello, ${name}!` }))
sensor('the greeting is {string}', (state) => state.greeting)

This is a thin stateful shell over the pure @oselvar/var-core. Adapters use the @oselvar/var/registry subpath for the registry-building glue; step authors never need it.