How do you test frontend projects against older Chrome versions without the headache?

Testing frontend projects against older Chrome or Chromium versions to reproduce browser-specific bugs has always been a bit painful.

Managing multiple versions manually, dealing with legacy web-view behaviours, or trying to spin up old binaries quickly becomes messy when you're deep into debugging.

I was running into this constantly while trying to track down tricky layout bugs on older browser builds, so I wanted something lightweight that lets me download, install, and seamlessly switch between local Chromium versions without breaking a sweat.

I ended up building Chromium Stack to solve this exact workflow bottleneck. It's a local tool designed specifically for checking browser compatibility and reproducing version-specific bugs quickly.

I'm curious how other frontend developers and makers handle testing across legacy browser versions:

• How do you usually test or reproduce bugs tied to specific older browser versions?'

• Do you rely on cloud testing platforms, Docker containers, or local binaries?

If you want to check it out, here is the project: https://1m93.github.io/Chromium-Stack/