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

qc-dom_utils

v0.1.1

Published

A set of utilities for working with the DOM.

Downloads

20

Readme

qc-dom_utils

Build Status License Downloads

npm badge

A set of utilities for working with the DOM. Utilities found in other major libraries such as jQuery will not be found here unless there is a good reason.

The structure of this package allows importing only the utilities used. See the Example Usage section below. If you choose, you can import the entire library or subsets of the library. All of which depends on how you script the import statements.

Installation

npm install --save qc-dom_utils

or

yarn add qc-dom_utils

Example Usage

// Import entire library
import DomUtils from 'qc-dom_utils'

let elem = DomUtils.get('myElem')
let formElem = DomUtils.form.get('myForm')
// Import just the `get` utility
import get from 'qc-dom_utils/get'

let elem = get('myElem')
// Import just the form subset of utilities
import FormUtils from 'qc-dom_utils/form'

let formElem = FormUtils.get('myForm')
let firstInvalidElem = FormUtils.focusFirstInvalid('myForm', {
  ...
  lastname: '...',
  addressLn1: '...',
  addressLn2: false,
  city: false,
  state: '...',
  ...
})
// Import just the `get` utility from the `form` namespace
import getForm from 'qc-dom_utils/form/get'

let formElem = getForm('myForm')
// Import just the `focusFirstInvalidInputControl` utility from the `form` namespace
import focusFirstInvalid from 'qc-dom_utils/form/focusFirstInvalidInputControl'

let firstInvalidElem = focusFirstInvalid('myForm', { ... })

Common JS

const DomUtils = require('qc-dom_utils/lib/cjs').default
...
const get = require('qc-dom_utils/lib/cjs/get').default
...
const FormUtils = require('qc-dom_utils/lib/cjs/form').default
...
const get = require('qc-dom_utils/lib/cjs/form/get').default
...
const focusFirstInvalid = require('qc-dom_utils/lib/cjs/form/focusFirstInvalidInputControl').default
...