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 🙏

© 2026 – Pkg Stats / Ryan Hefner

marvel-js-core

v1.0.0

Published

Work started off based on C# ProductAlpha, but I began to look at Marvel and the aim was to work towards something a bit more like that.

Downloads

0

Readme

MarvelJS Framework

Some things to know ...

Work started off based on C# ProductAlpha, but I began to look at Marvel and the aim was to work towards something a bit more like that.

cucumber.js requires files to be in certain folders. Therefore, if using the framework beforeScenarios and we want to use these functions, we need to add a hooks.js to the main test solution folder and import the beforeScenario. For example, create hooks.js and add a single line:

const hooks = require(../to/the/location/beforeScenarios)

Alternatively, you can use a world.js to setup your global context per scenario.

Timeouts!!! Cucumber js hooks time out after 5000ms by default. If using a wait for element which may take longer than 5000ms, set in the function setup. For example, take note of the object containing 'timneout' after the function name.

Then("I wait for element {string} to become present", {timeout: 2 * 5000}, async function(element) {

Setting up page objects - to set up a page object for steps, instantialise via the background feature in cucumber.

Running the example tests

script tag has been added in package.json file from the terminal run:

./node_modules/.bin/cucumber-js test/features/**/FrameworkTest.feature -f json:report.json && npm run htmlreport

To generate the report in html format

from the terminal run: node ./parent/core/reporting/generateReport.js