Post-processor for Polymer CSS polyfills
$ npm install --save polyfer
In a case that you are a task manager lover, please try gulp-polyfer or grunt-polyfer and have fun :)
var polyfer = require('polyfer');
polyfer('::content p { color: blue; }');
// => polyfill-next-selector { content: 'p' } ::content p { color: blue; }
polyfer('x-element ::content p {...}');
// => polyfill-next-selector {...} x-element ::content
polyfer(':scoped x-element p { color: blue; }');
// => polyfill-rule { content: 'x-element p'; color: blue; }
polyfer(':unscoped x-element p');
// => polyfill-unscoped-rule {...}
// since some preprocessors do not support /deep/ selectors
polyfer('body :deep a { outline: 1; }');
// => body /deep/ a { outline: 1; }
See examples comparing fixture.css(before) with expected.css(after).
$ npm install --global polyfer
$ polyfer input.css
$ polyfer input.css > output.css
$ polyfer --help
Keep in mind that all tasks run through Grunt.js.
git clone https://github.com/heldr/polyfer.git
cd polyfer
npm install
grunt watch
MIT © Helder Santana
FAQs
Post processor for Polymer CSS polyfills
The npm package polyfer receives a total of 5 weekly downloads. As such, polyfer popularity was classified as not popular.
We found that polyfer demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The official Go SDK for the Model Context Protocol is in development, with a stable, production-ready release expected by August 2025.
Security News
New research reveals that LLMs often fake understanding, passing benchmarks but failing to apply concepts or stay internally consistent.
Security News
Django has updated its security policies to reject AI-generated vulnerability reports that include fabricated or unverifiable content.