eslint-plugin-compat
ua-client-hints
Our great sponsors
eslint-plugin-compat | ua-client-hints | |
---|---|---|
7 | 13 | |
3,024 | 565 | |
- | 0.7% | |
5.1 | 4.2 | |
16 days ago | 22 days ago | |
TypeScript | Bikeshed | |
MIT License | GNU General Public License v3.0 or later |
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.
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.
- 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.
- 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.
ua-client-hints
- Példátlan leállás jöhet a neten, és nem is lesz egyszerű megoldani
-
Version 100 in Chrome and Firefox
I encourage you to review the decision making and engage in the discussion here: https://github.com/WICG/ua-client-hints
-
Google Chrome Update will cause Big Issue For 2 Billion Users
chrome is starting to implement UA-CH, which splits up user agent info into individual headers sent by the client: https://wicg.github.io/ua-client-hints/
-
JP Morgan Chase Bank, or Why Not to Whitelist Operating System User Agents
As a Firefox/FreeBSD user occasionally annoyed by this nonsense, but not being knowledgeable about modern web standards evolution, I wonder if https://wicg.github.io/ua-client-hints/ will fix this by killing User-Agent headers.
-
Mozilla alters stance on User-Agent Client Hints from “non-harmful” to “harmful”
There is a JS companion to this proposal that splits up the information in a similar way
-
User-Agent Client-Hints, take 2
First, the JavaScript API is widely open and does not require any delegation or even opt-in. IMO this is a privacy issue, and Apple seems to agree with me 🙂
- Firefox 85 Cracks Down on Supercookies
What are some alternatives?
stylelint-no-unsupported-browser-features - Disallow features that aren't supported by your target browser audience.
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
web - Pi-hole Dashboard for stats and more
stylelint-no-unsupported-browser-fe
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+
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
glasgow - Scots Army Knife for electronics