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

is-dom4-supported

v2.0.1

Published

does this JavaScript environment conform to DOM 4?

Downloads

4

Readme

is-dom4-supported.js npm module AppVeyor Status Travis CI Status

does this JavaScript environment conform to DOM 4?

What is this?

I wanted my web apps to be able to detect support for Polymer and the WebComponents poly-fills.

Combined with an ECMAScript 5 feature-detect, this project ought to answer the following questions:

  • does the environment support Polymer and WebComponents.js (lite)?
  • do I need to continue with a non-Polymer fallback?

I've checked and confirmed that this project tests all the parts of DOM 4 that WebComponents.js (lite) depends upon (plus some other things I'm interested in).

Supported Environments

I've manually tested in a range of environments:

  • true: Chrome (43), (Mobile) Safari (8), Firefox (38), Internet Explorer (10, 11), Edge

  • false: Internet Explorer (6, 7, 8, 9)

Usage

  • CommonJS (e.g. Node.js, Browserify, etc) use index.js
var isDOM4Supported = require('is-dom4-supported');
console.log(isDOM4Supported()); // `true` or `false`
<script src="dist/index.js"></script>
<script>
console.log(isDOM4Supported()); // `true` or `false`
</script>

WebComponents.js poly-fills CustomEvent and MutationObserver, so you'll probably want to ignore the results for these tests:

var isDOM4Supported = require('is-dom4-supported');
console.log(isDOM4Supported(null, {
  ignore: ['dom4.customevent', 'dom4.mutationobserver']
})); // `true` or `false`

API

isDOM4Supported(el, options)

  • @param {Element} [el] a DOM Element to run tests against
  • @param {SupportedOptions} [options]
  • @returns {boolean|Object} true|false unless returnObject is true

This project creates a temporary unattached DOM Element if you do not provide one. If you are performing other tests against DOM Elements, you might consider reusing the same one, hence the optional parameter.

The report Object contains the results of individual tests prefixed by their DOM level (e.g. "dom4.customevent"), as well as summary properties that are true if all preceding properties are true (e.g. "dom4").

@typedef {Object} SupportedOptions

  • @property {string[]} ignore - array of tests to ignore for summaries
  • @property {boolean} returnObject - if true, function returns a detailed Object