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

@pepfar-react-lib/test-console

v0.1.14

Published

**Repo Owner:** Ben Guaraldi [@benguaraldi](https://github.com/benguaraldi)

Downloads

9

Readme

DHIS2 Dev Tools

Repo Owner: Ben Guaraldi @benguaraldi

What does this library solve?

  1. Did you ever ask QA to test your app but they were testing an old version on another server?
  2. Does your QA team find themselves replicating the same scenario in your app over and over?

Solution for #1
If you add <DevTools> to your app then your tester can just press ~ on keyboard to open developers only console. There they can double-check build name & date of your app.

Solution for #2
You can automate any task in JavaScript as a function and then inject the function into <DevTools>. Your tester can then click a button in <DevTools> and save himself a lot of clicking.
We're using this for pre-filling elaborate search dialogs for each test scenario.

Example use

Usage

You can inject any method. Anything you need to automate in your app. Just wrap it into a method and inject into Dev Tools.

In the below example we want to automate searches by calling this.search method with different parameters.

import {DevTools, registerDevMethod} from "@pepfar-react-lib/test-console";

export default class SearchForm extends React.Component {
    constructor(props) {
        const searches = [
            {name: '1. Rwanda', method: () => this.search('Rwanda', '2020Q4')},
            {name: '2. Nigeria', method: () => this.search('Nigeria', '2020Q4')},
        ];
        searches.forEach(registerDevMethod);
    }

    search(ou: string, period: string) {
        // your code
    }

    render() {
        return <React.Fragment>
            <MyAwesomeSearchForm onSearch={this.search}/>
            <DevTools buildName={'Dedupe search added'} buildDate={new Date()}/>
        </React.Fragment>
    }
}