How not to lose your mind in a world where browsers ship every two weeks

How do you know it?

Yeah,
whatever 🙄

Major browser releases

🎂 Once a year

Release per browser in old times

🚀 6–8 a year

Releases per browser in 2010s

🔥 12 a year

Releases per browser in 2020s

70+

Major browser releases by the end of 2026

What’s
the pipeline?

collector.openwebdocs.org

Manualy runs for every beta version

mdn/browser-compat-data

2M weekly downloads

unpkg.com/@mdn/browser-compat-data

web-platform-dx/web-features

450K weekly downloads

unpkg.com/web-features/data.json

But…
Can I use?

Signals
for developers

Baseline

More tools? Yes

Now enforce it

Baseline as a target

"browserslist": [
  "baseline widely available"
]

Also: baseline newly available or baseline 2024

Pin it for reproducible builds

"browserslist": [
  "baseline widely available on 2024-06-06"
]

Native since Browserslist 4.26 — no extra package needed.

Target your actual users 🇬🇪

"browserslist": [
  "cover 99.5% in GE"
]

Don’t forget, config strings can be combined!

Lint your CSS

// eslint.config.js
export default [{
	files: ["**/*.css"],
	plugins: { css },
	language: "css/css",
	rules: {
		"css/use-baseline": ["error", { available: "widely" }]
	}
}];

Same idea, everywhere

But… LLMs!

The models we use were trained on the web that was, not the web that is.

aifoc.us/please-mind-the-model-gap

Fix the 🤖

Give it real docs

			claude \
				mcp add --transport http \
				mdn https://mcp.mdn.mozilla.net/
		

The MDN MCP server provides access to latest docs and compat data.

Give it modern habits

			/plugin marketplace add GoogleChrome/modern-web-guidance
			/plugin install modern-web-guidance@googlechrome
		

Modern Web Guidance inject current patterns and compat data.

Signals
from for developers

Use
new features

Build
new tools

Use the data,
speak up!