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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@valdres/browser-screen-details

v1.0.0-beta.5

Published

Reactive multi-screen layout from the Window Management API

Readme

browser-screen-details

Wraps the Window Management API (window.getScreenDetails()) as global atoms exposing the current screen, all connected screens, and the permission state.

Permission required

Screen details are empty until you call requestScreenDetails(), which prompts for the window-management permission. Requires a secure context.

Install

bun add @valdres/browser-screen-details

Live example

▶ Live example: https://valdres.dev/react/plugins/browser-screen-details

Usage

import { useValue } from "valdres-react"
import {
    currentScreenAtom,
    screensAtom,
    screenPermissionAtom,
    requestScreenDetails,
} from "@valdres/browser-screen-details"

function Screens() {
    const permission = useValue(screenPermissionAtom)
    const current = useValue(currentScreenAtom)
    const screens = useValue(screensAtom)

    if (permission !== "granted")
        return <button onClick={() => requestScreenDetails()}>Allow screens</button>
    return (
        <div>
            {current?.label}: {current?.width} × {current?.height} ({screens.length} screens)
        </div>
    )
}

Exports

| Export | Kind | Type | | ----------------------- | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | currentScreenAtom | atom (read-only) | ScreenDetail \| null | | screensAtom | atom (read-only) | ScreenDetail[] | | screenPermissionAtom | atom (read-only) | ScreenPermissionState | | requestScreenDetails | util fn | () => Promise<ScreenDetail[] \| null> | | ScreenDetail | type | { label, left, top, width, height, availLeft, availTop, availWidth, availHeight, colorDepth, pixelDepth, devicePixelRatio, orientationType, orientationAngle, isPrimary, isInternal } | | ScreenPermissionState | type | "prompt" \| "granted" \| "denied" \| "unsupported" |

Cross-framework

All state is global atoms, so it works in every framework — only the read primitive differs. The atoms stay empty until requestScreenDetails() resolves; call it once from anywhere.


Full documentation: https://valdres.dev/react/plugins/browser-screen-details