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

brut-js

v0.0.8

Published

Custom Elements Available via BrutRb

Downloads

442

Readme

brut-js

Utility Custom Elements and JS for BrutRB

This provides utility custom elements for use in a BrutRB-powered app, as well as a rudimentary testing system for testing custom elements.

Install

npm install brut-js

If you want to write tests for custom elements, you must also install JSDOM and Mocha:

npm install --save-dev jsdom mocha

Using Custom Elements

The simplest way is to import them all and define them:

import { BrutCustomElements } from "brut-js"
document.addEventListener("DOMContentLoaded", () => {
  BrutCustomElements.define()
})

See the jsdocs for what elements are available.

Testing of Custom Elements

This library contains rudimentary support for testing custom elements using jsdom. It attempts to use the elements as they would in a real browser, and your tests and assertions should interact with the elements using the DOM and not directly.

A simple example is the test for BrutAutosubmit/<brut-automsubmit>, which enables any form element to automatically submit the form it's a part of:

<form>
  <brut-autosubmit>
    <input type="text">
  </brut-autosubmit>
  <button>Submit</button>
</form>

When the <input> above dispatches a "change" event, the <form> is submitted. You can see in the test file that each test locates the form and the input, dispatches an event from that input, then checks to see if the form was submitted, all using the browser's APIs.

Testing Your Custom Elements

  1. Set up Mocha

    npm install --save-dev mocha
  2. Create a location for your tests:

    mkdir specs/js # can be anything
  3. Create a tautoloigical test to ensure your setup is working:

    // specs/js/canary.spec.js
    import { withHTML } from "../src/testing/index.js"
    describe("<my-custom-element>", () => {
      withHTML(`
        <my-custom-element>OK</my-custom-element>
      `).test("Tests work", ({document,assert}) => {
         const element = document.querySelector("my-custom-element")
         assert.equal(element.textContent,"OK")
      })
    })
  4. Run mocha:

    npx mocha specs/js --extension spec.js --recursive

Development

  1. Install Docker

  2. Set up your dev environment:

    dx/build
  3. Start the dev environment

    dx/start
  4. In another terminal, set everything up

    dx/exec bin/setup
  5. Run all tests

    dx/exec bin/ci
  6. Run a single test

    dx/exec npm run bundle
    dx/exec npm run test:one specs/File.spec.js

Remember to run npm run bundle any time you change files in src, as the tests bring in the code via a bundle produced by that task.