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

lovecraft

v1.0.3

Published

A dark and eldritch test framework, powered by the ancient tomes of [Mocha](https://mochajs.org/), [Chai](https://www.chaijs.com/), [Sinon](https://sinonjs.org/), and [c8](https://github.com/bcoe/c8#readme).

Downloads

334

Readme

Lovecraft Test Framework 🐙

A dark and eldritch test framework, powered by the ancient tomes of Mocha, Chai, Sinon, and c8.

Features 🧠

  • Re-exports all functions and assertions from the chai module, allowing you to use them directly in your tests.
  • Re-exports all functions from the sinon module, providing powerful mocking and stubbing capabilities.
  • Exposes a CLI command lovecraft that can be used to run your tests, with optional linting and coverage reporting.

Usage 🪄

Import the Lovecraft framework into your project:

import lovecraft from 'lovecraft';

const { expect, stub } = lovecraft;

// Use the imported test utilities in your code

The lovecraft module provides a default export that can be used to run tests, lint your code, and generate coverage reports. The available command-line options are:

Test 🧪

  • lovecraft or lovecraft -t or lovecraft --test: Runs all tests found in **/*.test.js files.

Coverage 📊

  • lovecraft -c or lovecraft --coverage: Runs tests with coverage reporting.

Lint 🧹

  • lovecraft -l or lovecraft --lint: Runs ESLint on your code.

Publish 🚀

  • lovecraft -p or lovecraft --publish: Bumps the version, then tags and publishes the package.

When using the --publish option, Lovecraft will run all the other checks (test, lint, coverage) first. The package will only be published if all the checks pass successfully. This can be used to prevent the accidental publication of a package with failing tests or linting issues.

All 🔮

  • lovecraft -a or lovecraft --all: Runs tests, generates coverage, and lints the code.

Note that "all" means "all checks" in this context; it does not publish the package. However, lovecraft --all --publish is a great way to ensure that all checks pass before publishing the package.

Conventions 🕸️

Lovecraft assumes that your test files follow the convention of being named *.test.js and located alongside the code they are testing. This allows the CLI command to easily find and run the appropriate tests.

The Lovecraft framework also includes a default ESLint configuration file (eslint.config.js) that can be used to ensure consistent code style and quality.

If you have any other questions or need further assistance, please don't hesitate to reach out to the dark masters of Phantomaton AI. 🐙