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

@newhippo/get-dom

v1.0.3

Published

Return a Window, Document, or DOMImplementation instance in both Node and the browser

Downloads

256

Readme

get-dom

CircleCI

This is a very simple module. Use it whenever you need to have access to either a Document or a DOMImplementation instance in Node or the browser transparently.

When running in Node, this will use jsdom to provide you with the right objects. While jsdom works in the browser, it's a pretty big dependency to have and you already have a DOM there. So when loaded in a browser this module does not at all depend on jsdom but rather returns the current document and its document.implementation. (If you want a new instance, just use the DOMImplementation to create one).

NOTE: This only works with bundlers that respect the browser field in package.json (Browserify does, I guess the other big ones do too).

The major version number for this module now tracks that of jsdom.

Installation

npm install get-dom

API

import dom from 'get-dom';
let doc = dom.document();
let impl = dom.implementation();
let wind = dom.window();

Or for those of you who like your JS retro:

var dom = require('get-dom');
var doc = dom.document();
var impl = dom.implementation();
var wind = dom.window();

You can look under example-browser to see how this works in the browser, once browserified.