semver
browserslist
semver | browserslist | |
---|---|---|
7 | 55 | |
4,962 | 12,730 | |
0.6% | 0.5% | |
7.0 | 7.8 | |
6 days ago | about 2 months ago | |
JavaScript | JavaScript | |
ISC 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.
semver
-
The curious case of semver
Yeah, but it talks about the semver package, which is related and why it caused performance issues
-
Release NPM Package With Automatic Versioning
This release script increments the version number of the package and publishes the package to the NPM registry (or other registry). To correctly increment the version number, npm's semver package automatically finds the next version number according to the specified level minor (major/minor/patch).
-
Symbols in package.json
In a later post, I shall be sharing some actual examples using node-semver, which is the tool that npm uses to parse these Semantic Versioning Complaint dependencies version.
-
npm-registry-firewall
{ "server": { "host": "localhost", // Defaults to 127.0.0.1 "port": 3000, // 8080 by default "secure": { // Optional. If declared serves via https "cert": "ssl/cert.pem", "key": "ssl/key.pem" }, "base": "/", // Optional. Defaults to '/' "healthcheck": "/health", // Optional. Defaults to '/healthcheck'. Pass null to disable "keepAliveTimeout": 15000, // Optional. Defaults 61000 "headersTimeout": 20000, // Optional. Defaults 62000 "requestTimeout": 10000 // Optional. Defaults 30000 }, "firewall": { "registry": "https://registry.npmmirror.com", // Remote registry "entrypoint": "https://r.qiwi.com/npm", // Optional. Defaults to `${server.secure ? 'https' : 'http'}://${server.host}:${server.port}${route.base}` "base": "/", // Optional. Defaults to '/' "rules": [ { "policy": "allow", "org": "@qiwi" }, { "policy": "allow", "name": ["@babel/*", "@jest/*", "lodash"] // string[] or "comma,separated,list". * works as .+ in regexp }, { "policy": "deny", "name": "colors", "version": ">= v1.4.0" // Any semver range: https://github.com/npm/node-semver#ranges }, { "policy": "deny", "license": "dbad" // Comma-separated license types or string[] }, { "policy": "allow", "username": ["sindresorhus", "isaacs"] // Trusted npm authors. }, { "policy": "allow", "name": "d", // `allow` is upper, so it protects `< 1.0.0`-ranged versions that might be omitted on next steps "version": "< 1.0.0" }, { "policy": "deny", // Checks pkg version publish date against the range "dateRange": ["2010-01-01T00:00:00.000Z", "2025-01-01T00:00:00.000Z"] }, { "policy": "allow", "age": 5 // Check the package version is older than 5 days. Like quarantine } ] } }
-
Package.json File explained!!!
Note: ~ and ^ you see in the dependency versions are notations for version ranges defined in semver as it follows semantic versioning.
-
SemVer - 0.x.x
To prevent potential breaking changes, when you do a minor update of a dependency, NPM treats versions a bit different:
-
One-stop shop for working with semantic versions in your GitHub Actions workflows
Yeah, it's basically a wapper around semver package, so the outputs may look familiar to you. But if you need more in your workflows — feel free to open an issue with a feature you’re missing.
browserslist
- Browserslist/browserslist: `not and_UC all`
-
Shoelace: A forward-thinking library of web components
Not these days, where most people are using evergreen browsers and iOS users upgrade very quickly.
Take a look at the defaults for browserslist, for example:
https://browsersl.ist/#q=defaults
It just barely supports Safari 15, on iOS only, and that’s likely to go away imminently because it’s under 1% usage.
-
How to Clone an Object in JavaScript
browserslist
-
How we improved page load speed for Next.js ecommerce website by 1.5 times
We compile JS only for modern browsers. The list of default browsers in Next can be overridden in your browserslist.
-
The Need for Speed: Next.js Performance Overhaul with Polyfills and SWC
In the latest versions of Next.js, targeting specific browsers or features is a breeze using the Browserslist configuration in your package.json file. The latest version of Next.js (v13) uses the following configuration by default:
-
How can I find out if I should support IE 9/10/11?
For a more general answer to browser support, check out https://github.com/browserslist/browserslist. That seems to be standard tool to help you with that.
-
WebGPU hits 40% availability 2 weeks after Chrome releases support
As someone else pointed out, you're overestimating Chrome/ium's market share.
Regardless, after the web.dev/baseline announcement, I looked at Browslerlist and one of our site's analytics and it is shocking how many people are not using the last two versions of evergreen browsers. There is a long tail of browser versions in those stats.
https://browsersl.ist
-
Baseline: a unified view of stable web features
The way folks handle this in production is with browserslist, which lets you query on different things you want to support: https://github.com/browserslist/browserslist. This in turn tells other parts of your tooling what language features to transpile for production.
I imagine tools could be built on top of that which do what you’re asking too
- Browserslist
-
Configure Stimulus with esbuild and Babel — Rails & Javascript
# .browserslist.rc # Babel Preset configuration # -------------------------- # Defines web-browser compatibility parameters for Babel to transpile your JS code. # This configuration is used by babel.config.js. # More information in here. # https://github.com/browserslist/browserslist # Support browsers with a market share higher than 5% >10%
What are some alternatives?
husky - Git hooks made easy 🐶 woof!
autoprefixer - Parse CSS and add vendor prefixes to rules by Can I Use
dotenv - Loads environment variables from .env for nodejs projects.
parcel - The zero configuration build tool for the web. 📦🚀
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
caniuse - Raw browser/feature support data from caniuse.com
os-locale - Get the system locale
rollup-plugin-postcss - Seamless integration between Rollup and PostCSS.
opencv - OpenCV Bindings for node.js
ECMAScript 6 compatibility table - ECMAScript compatibility tables
hypernova - A service for server-side rendering your JavaScript views
rollup-plugin-terser - Rollup plugin to minify generated bundle