dom-support is a JavaScript library originally extracted from jQuery, designed to detect various browser rendering and styling quirks. It provides a simple object where properties (e.g., `opacity`, `leadingWhitespace`, `boxSizing`) are booleans indicating support or specific browser behaviors that deviate from standards. The package version 0.0.2 was last published over a decade ago. It addresses issues prevalent in browsers like IE6/7/8, older WebKit, and pre-standard implementations. This library is now largely obsolete as modern browsers have converged on standards, making its checks mostly irrelevant for contemporary web development. It has no discernible release cadence and is no longer actively maintained. Its primary differentiator was its comprehensive set of quirk detections based on extensive real-world testing from a major library like jQuery.
npm install dom-supportVerified import paths — ran on the pinned version, not inferred.
Initializes the dom-support library and logs a selection of detected browser quirks. Demonstrates how to access feature flags.
Do not use this package in new projects. For modern feature detection, rely on built-in browser APIs or a maintained, targeted polyfill/feature-detection library (e.g., Modernizr, although even that is less critical today).
If you absolutely must use this deprecated package in a modern ESM context, configure your bundler to handle CommonJS modules (e.g., using `@rollup/plugin-commonjs` for Rollup) or use `require()` in a CJS file and then import that CJS file.
Thoroughly understand the specific quirk being detected if you are using this library. For contemporary feature detection, prefer `typeof window.CSS.supports === 'function'` or direct property checks (`'property' in document.body.style`).
This package is CommonJS. Use a bundler like Webpack or Rollup configured to handle CJS modules, or rewrite your code to use native ESM imports for modern libraries. This package is not designed for direct ESM usage.
This package does not export a default or named export for ESM. It only provides a CommonJS `module.exports`. If you must use it, you'll need a CommonJS interop solution in your build pipeline or to stick to `require()` in a CJS context.
No dependency data recorded yet.