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

mithril-testing-library

v1.0.7

Published

This library provides some helper functions around [@testing-library/dom](https://github.com/testing-library/dom-testing-library) for testing mithril components.

Downloads

8

Readme

mithril-testing-library

This library provides some helper functions around @testing-library/dom for testing mithril components.

Installation

npm install --dev mithril-testing-library

or using yarn

yarn add --dev mithril-testing-library

This library has peerDependencies for mithril.

Difference from react-testing-library

This library takes a lot of code from react-testing-library. The main difference is the way the render function is called.

In mithril-testing-library, the render function is called with the mithril Component and the attributes you want to pass the component as arguments. react-testing-library on the other hand works by sending the react element directly to the render function.

That won't work in mithril since if we create mithril element outside of mithril tree construction, the event callbacks for those elements won't trigger an automatic redraw in mithril. The reference check for vnode returned by that element created outside mithril tree would always return the same object.

Here's more information on the mithril documentation site

https://mithril.js.org/components.html#avoid-creating-component-instances-outside-views

Examples

async function wait(waitTime) {
  return new Promise((res) => setTimeout(res, waitTime));
}

const ComponentToTest = {
  view: (vnode) => {
    return m("div", [
      m(
        "button",
        {
          onclick: (e) => {
            e.stopPropagation();
            vnode.state.showList = !vnode.state.showList;
          },
        },
        "Open list"
      ),
      vnode.state.showList &&
        m(
          OnClickOutside,
          {
            onDocumentClick: () => {
              vnode.state.showList = false;
              // since this click handler is outside mithril ecosystem, we 
              // have to force redraw
              m.redraw();
            },
          },
          m("ul", { "data-testid": "the-list" }, [(m("li", 1), m("li", 2))])
        ),
    ]);
  },
};

test("onclickoutside to close dropdown menu", async () => {
  const { getByText, queryByTestId } = render(ComponentToTest);
  expect(queryByTestId("the-list")).toBeNull();
  fireEvent.click(getByText("Open list"));

  await waitFor(() => {
    expect(queryByTestId("the-list")).not.toBeNull();
  });

  await wait(1);
  fireEvent.click(document);

  await waitFor(() => {
    expect(queryByTestId("the-list")).toBeNull();
  });
});