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

element-box

v1.0.1

Published

Work easily with an element's position and dimensions

Downloads

20

Readme

element-box

Work easily with an element's position and dimensions

Gzipped Size Build Status

Install

npm install element-box

Why

I work with the dimensions and positions of elements rarely enough to forget the details, but often enough to frustrate me when it hampers my flow and productivity:

  • Did element.getBoundingClientRect() include the borders or not?
  • What was the difference between clientWidth and offsetWidth?
  • How do I get the window dimensions? Should I use document.documentElement for that, or not?

This library is both an abstraction and a thinking model for DOM dimensions and position. It adds functions that are otherwise time-consuming to write on your own.

API

getContentBox(element: HTMLElement): DOMRect

Element's dimensions without border, padding, and margin — element.getBoundingClientRect() - border - padding.

getPaddingBox(element: HTMLElement): DOMRect

Element's dimensions with padding but without border and margin — element.getBoundingClientRect() - border.

getBorderBox(element: HTMLElement): DOMRect

Equivalent to element.getBoundingClientRect().

getMarginBox(element: HTMLElement): DOMRect

Element's dimensions with padding, border, and margin — element.getBoundingClientRect() + margin.

getWindowBox(): DOMRect

Something like window.getBoundingClientRect() if it existed. If you are wondering, document.documentElement.getBoundingClientRect() won't probably do what you want.

getElementBox(element: HTMLElement, options): DOMRect

Would be easier to show you examples:

// like that:
getElementBox(element, {
    includePadding: true,
    includeBorder: false,
    includeMargin: false
})

// or like that:
getElementBox(element, 'content-box')
getElementBox(element, 'padding-box')
getElementBox(element, 'border-box')
getElementBox(element, 'margin-box')