![Introducing Enhanced Alert Actions and Triage Functionality](https://cdn.sanity.io/images/cgdhsj6q/production/fe71306d515f85de6139b46745ea7180362324f0-2530x946.png?w=800&fit=max&auto=format)
Product
Introducing Enhanced Alert Actions and Triage Functionality
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
es-feature-tests
Advanced tools
Readme
Feature Tests for JavaScript. This is the library used by the FeatureTests.io service.
Load the library, request feature test results for the current browser, use those results to determine what code to deliver for your application!
If all the JavaScript features/syntax your code uses are supported natively by the browser, why would you load up the ugly transpiled code? Why would you load dozens of kb of polyfills/shims if all (or most of) those APIs are already built-in?
Just use the original authored ES6+ code in newest browsers! Only use transpiled code and polyfills/shims for browsers which are missing the features/syntax you need.
Don't rely on stale caniuse data baked into build tools that matches a browser based on brittle UserAgent string parsing. Feature Test! That's the most reliable and sensible approach.
The updated and detailed documentation for how this library works and what test results are available can be found on FeatureTests.io/details.
Hosting this package locally on your server is mostly useful if you want to use the feature tests in your Node/iojs programs (see "Node/iojs" below).
You can install this package locally and web host your own copy of the library files if you prefer. You'll need to modify the URLs ("https://featuretests.io") in several places to get them to load correctly. Hosting the files also means the test results won't be shareable with other sites, which puts more testing burden on users' machines.
It's probably a much better idea to use the "https://featuretests.io" service's hosted versions of the files for web usage.
Using this library on the web:
<script src="https://featuretests.io/rs.js"></script>
<script>
window["Reflect.supports"]( "all", function(results,timestamp){
console.log( results );
// {
// ..
// }
});
</script>
Using this library in Node/iojs:
npm install es-feature-tests
Then:
var ReflectSupports = require("es-feature-tests");
ReflectSupports( "all", function(results,timestamp){
console.log( results );
// {
// ..
// }
});
If you install this package from GitHub instead of npm, you won't have the deploy/*
files for deployment. Run these commands from the main repo directory to build them:
npm install
npm run build
The code and all the documentation are all (c) 2015 Kyle Simpson and released under the MIT license.
FAQs
Feature Tests for JavaScript
The npm package es-feature-tests receives a total of 3 weekly downloads. As such, es-feature-tests popularity was classified as not popular.
We found that es-feature-tests 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.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.