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

safe-get-element

v1.0.3

Published

Type safe document.getElementById

Downloads

8

Readme

safe-get-element

Runtime-based type safety for the commonly used document.getElementById method. This method prevents you from having to manually check if a returned element is not null, and you can optionally provide a tagName that will assert the given element type.

Quick Start

npm i safe-get-element
<!DOCTYPE html>
<html>
  <button id='my-button'></button>
</html>
import { safeGetElement } from 'safe-get-element'

const button = safeGetElement('my-button', 'button') // HTMLButtonElement

// without safe-get-element

const button = document.getElementById('my-button')

if (button === null) {
  throw new Error('Cannot find button!')
}

if (button.tagName !== 'BUTTON') {
  throw new Error('Button is not of type HTMLButtonElement')
}

API

safeGetElement(id: string)

Returns: HTMLElement

When used with just an id, the API will assert the queried element is not null and return it. Otherwise, it throws an error.

safeGetElement(id: string, assertType: TagName)

TagName is a generic that is constrained to keyof HTMLElementTagNameMap from TypeScript's lib.dom.d.ts.

Returns: HTMLElementTagNameMap[TagName]

When passed an assertType, the API asserts the queried element eixsts and its respective tagName matches the associated assertType. If it does, it returns the element as the associated DOM Interface.

What about getElementsByTagName, querySelector, or querySelectorAll?

These methods already support some level of type safety!

// getElementsByTagName
const buttons1 = document.getElementsByTagName('button') // HTMLCollectionOf<HTMLButtonElement>
const myButton1 = buttons.find(button => button.id === 'my-button') // HTMLButtonElement

// querySelector
const myButton2 = document.querySelector('button') // HTMLButtonElement | null

if (myButton2 !== null) {
  // HTMLButtonElement
}

// querySelectorAll
const buttons2 = document.querySelectorAll('button') // NodeListOf<HTMLButtonElement>
const myButton3 = buttons.find(button => button.id === 'my-button') // HTMLButtonElement