Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

A list of tests to determine whether an `@supports` rule is considered a browser hack

License

Notifications You must be signed in to change notification settings

projectwallace/css-at-supports-browser-h4cks-analyzer

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

css-at-supports-browser-h4cks-analyzer

Build Status Known Vulnerabilities Dependencies Status Dependencies Status XO code style Project: Wallace

A list of tests to determine whether an @supports is a browser hack, derived from the formidable browserhacks.com (Repo).

Installation

npm install css-at-supports-browser-h4cks-analyzer

# or

yarn add css-at-supports-browser-h4cks-analyzer

Usage

const isBrowserHack = require('css-at-supports-browser-h4cks-analyzer')

// @supports rule example => @supports (display: grid) { .selector { } }
console.log(isBrowserHack('(-moz-appearance:meterbar)'))
// => true

console.log(isBrowserHack('(display: grid)'))
// => false

Related projects

  • CSS Analyzer - CSS statistics module
  • Wallace CLI - CSS statistics in your CLI
  • CSS Analyzer Diff - Calculates the diff between two sets of CSS analysis
  • Color Sorter - Sort CSS colors by hue, saturation, lightness and opacity
  • Gromit CLI - A test framework to assert that CSS statistics don't exceed certain thresholds.

License

MIT © Bart Veneman

About

A list of tests to determine whether an `@supports` rule is considered a browser hack

Resources

License

Stars

Watchers

Forks

Packages

No packages published