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

test-timebomb

v1.0.0

Published

đź’Ą auto expire features in your code Edit

Downloads

3

Readme

test-timebomb

đź’Ą auto expire feature toggles in your code

example

import timebomb from 'test-timebomb';

// jest it up (optional - default will simply throw)
timebomb.fail = (test) => expect('đź’Ą').toEqual('feature ' + test.result.description + ' has expired')

// yeah thats a ms timestamp for when this test will never pass again
timebomb(1496327291228)(
  test('myFeature', () => {
    expect(feature()).toMatchSnapshot();
  })
)

output:

//output
FAIL  __tests__/feature.test.js
 â—Ź Test suite failed to run

   expect(received).toEqual(expected)

   Expected value to equal:
     "feature myFeature has expired"
   Received:
     "đź’Ą"

default timebomb.fail simply throws:

FAIL  __tests__/feature.test.js
 â—Ź Test suite failed to run

   đź’Ąfeature expiredđź’Ą

why does this exist?

There are many scenarios where code depends on time sensitive implementations. Maybe it's your Firebase or AWS account info, or some Signing Certificates. If your build breaks before any of these scenarios expire they force development to correct before an outage.

Another use case is for features that you know will be deprecated can loudly be set to be cleaned up in your codebase.