Package Exports
- prefix-property
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (prefix-property) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Prefix Property

An in-browser vendor prefixer that doesn't suck.
Simple usage:
import prefix from 'prefix-property';
// or
const prefix = window.prefixProperty;
// in chrome:
prefix('fontFeatureSettings'); // => 'WebkitFontFeatureSettings'
prefix.css('fontFeatureSettings'); // => '-webkit-font-feature-settings'
Advanced usage:
import { js, css, jsPrefix, cssPrefix } from 'prefix-property';
// in chrome:
js('fontFeatureSettings'); // => 'WebkitFontFeatureSettings'
js('font-feature-settings'); // => 'WebkitFontFeatureSettings'
css('fontFeatureSettings'); // => '-webkit-font-feature-settings'
css('font-feature-settings'); // => '-webkit-font-feature-settings'
// browser's prefix:
jsPrefix(); // => 'Webkit'
cssPrefix(); // => '-webkit-'
// non-prefixed properties:
js('color'); // => 'color'
js('background-color'); // => 'backgroundColor'
The default output of prefixProperty() is a JS-friendly prop (ex: WebkitTransformOriginX).
To get a CSS-friendly prop, use prefixProperty.css() (ex: -webkit-transform-origin-x).
Installation
npm i prefix-property --saveor add /dist/prefix-property.min.js to your html.
Contributing
Clone repo, cd into it, then
npm install && npm run build && npm testBuilding
npm run buildTesting
Run the tests on your browser here.
npm testFor live retesting:
npm run test-watchBrowser:
npm run build && open test/test.htmlNode:
npm run test-nodeLinting
npm run lintLicense
MIT