access-key-label-polyfill
eslint-plugin-compat
| access-key-label-polyfill | eslint-plugin-compat | |
|---|---|---|
| 1 | 7 | |
| 1 | 3,041 | |
| - | - | |
| 3.2 | 4.3 | |
| over 3 years ago | 7 days ago | |
| TypeScript | TypeScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
access-key-label-polyfill
-
Boy, was it hard to implement proper keyboard shortcuts
I built a polyfill for the accessKeyLabel property that reveals the keyboard shortcut assigned by the browser and based on the accessKey property assigned to an interactive element. Browsers use different shortcuts for this and the accessKeyLabel property is the best way to improve the discoverability of custom shortcuts in web applications. Native support is missing in Chrome, IE and Edge. My AccessKeyLabelPolyfill is bridging the gap with less than 1 KB. GitHub | Demo
eslint-plugin-compat
-
Is there an open source tool for analyzing JS/CSS compatibility with different browsers?
I've looked for this in the past. There's not much for this that is totally comprehensive. You might find success with eslint-plugin-compat which will error when using things that aren't supported in your browsers.
- Comparing Babel, Sucrase, and Similar Libraries
- Is there a plugin (for Jetbrains IDEs) to check javascript code compatibility for certain browser versions?
- Question about minimum browser compatibility
-
JP Morgan Chase Bank, or Why Not to Whitelist Operating System User Agents
eslint-plugin-compat [0] and stylelint-no-unsupported-browser-features [1] can help you know when you're using an unsupported browser feature.
[0] https://github.com/amilajack/eslint-plugin-compat
- Facts every web dev should know before they burn out and turn to painting
-
[AskJS] Best practices for polyfills in libraries?
For now I'm trying to set up [eslint-plugin-compat](https://github.com/amilajack/eslint-plugin-compat) to check it for me, but I'm not sure it works — get 0 errors and 3 polyfills for a test snippet.
What are some alternatives?
chakra-ui - ⚡️ Simple, Modular & Accessible UI Components for your React Applications
stylelint-no-unsupported-browser-features - Disallow features that aren't supported by your target browser audience.
PolyFull - supercharge javascript applications
xournalpp - Xournal++ is a handwriting notetaking software with PDF annotation support. Written in C++ with GTK3, supporting Linux (e.g. Ubuntu, Debian, Arch, SUSE), macOS and Windows 10. Supports pen input from devices such as Wacom Tablets.
browserslist - 🦔 Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-preset-env
rollup-plugin-ts - A TypeScript Rollup plugin that bundles declarations, respects Browserslists, and enables seamless integration with transpilers such as babel and swc
chromium-legacy - Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+
stylelint-no-unsupported-browser-fe
fusionjs - Modern framework for fast, powerful React apps
deno - A modern runtime for JavaScript and TypeScript.
businesscard-linux - A Buildroot distribution small enough to run on my business card
ECMAScript 6 compatibility table - ECMAScript compatibility tables