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

dom-point-state

v1.0.3

Published

The state of a point in the DOM

Downloads

8

Readme

dom-point-state

Install

npm install --save dom-point-state

Example

import {getGlobalPointStateFactory} from 'dom-point-state';
const getGlobalPointState = getGlobalPointStateFactory();
let point = getGlobalPointState();
//Show the x/y coordinates of the pointer
let showx = document.querySelector('#showx');
let showy = document.querySelector('#showy');

window.addEventListener('mousemove', e=>{
    showx.textContent = point.x;
    showy.textContent = point.y;
});

API

getGlobalPointStateFactory()

This returns a getGlobalPointState() function.

getGlobalPointState()

Get the window point.

The window point returned from getGlobalPointState() is a singleton. You'll still have access to the destroy method, but make sure you really do want to use destroy. A destroyed window point will be destroyed for all references to it.

Use the side effects of the window point singleton to manage memory usage. For some things you might not want side effects. If so use getPointState(element) instead.

getPointState(element)

Get a point for a specific element. point.x, and point.y will still be relative to the window view port.

Point methods

point.destroy()

Clean up the a point you don't want to use any more.

point.inside(element)

Check if the point is inside an element. Especially child elements of the element the point belongs to.

Point properties

point.x, point.y

The x, and y integer coordinates of the point.

point.down, point.up

Is the point down, or up. This refers to the input device (mouse, touch).

The values of up, and down are boolean.

point.alive

Has the destroy method been called. If so point.alive returns false.

point[0], point[1], point.length

The point simulates an array. point[0] is equal to point.x, and point[1] is equal to point.y. point.length will always be equal to 2.

About

This libarary is optimized for usage on many elements. Use getGlobalPointState() for optimal memory, and event usage.

dom-point-state is meant for low level management of pointer position.

There are many properties on a point instance. Many aren't shown here. Print the object to see more.

x/y coordinates are retrieved from mousemove, and touchmove events. And dom-point-state is cross browser.