Published: July 1, 2025
June has come and gone, and with it, more happenings with Baseline. Settle in for another edition of the Baseline monthly digest, and get up to speed with all that's happened in the last month.
The New Stack covers Baseline
We've been seeing a bit more coverage of Baseline across the web recently, and it's been exciting to see. We talk about Baseline here on web.dev quite a lot—and for good reason—but what really matters is how the community talks about Baseline, because it gives us an idea of how it's being received.
Last month, The New Stack wrote a piece on Baseline. Their article was a great approach to what Baseline is trying to do—namely that it doesn't necessarily tell you what features to use or not use, but rather an outline of the problem of feature adoption in the past, and how Baseline could help make that an easier call to make. Check it out!
Baseline Newly and Widely available features
In the month of June, two features became Baseline Widely available:
Additionally, we recently published a post on JSON module scripts, which became Baseline Newly available in late April.
Vite 7.0 now targets Baseline Widely available
Vite 7.0 was recently released, and as a part of that major version release, it now targets Baseline Widely available by default. This is incredible news, because we often see that Baseline Widely available has broad support across the core browser set in most cases, as it includes features that have been available for 30 months.
Because of this, Baseline Widely available is a good default target. As it's a moving target that includes increasingly more features as time goes on, it also helps to make sure that you don't get left in the past.
Whether or not Baseline Widely available is the right target for you depends on the type of application you're building, as well as the target audience. For most people it's a solid choice—and Vite now does that for you—but if you're interested in diving deep on this topic, read more about how to choose a Baseline target for your project.
vscode.dev and codesandbox.io have inherited Baseline messaging
During Google I/O, we announced that Visual Studio Code implemented Baseline messaging for CSS and HTML features. This was a major development for Baseline tooling, and other IDEs based on Visual Studio Code will eventually—if not already—inherit this feature.
Some good news is that the web version of Visual Studio Code—vscode.dev—now offers Baseline messaging for HTML and CSS features. Not to be outdone, codesandbox.io—also based on Visual Studio Code—offers Baseline messaging as well.
We're excited to see increasingly more tooling adopting Baseline to help developers decide which web features are safe to use. As time goes on, we expect to see it in more tooling—from IDEs to linters to other parts of the developer experience.
That's a wrap
As well as all the I/O announcements, we've seen a lot of great developments in all things Baseline, especially from a tooling perspective. The month of May has been a great success, and that momentum will carry forward through the rest of the summer!
As usual, let us know if we missed anything Baseline-related, and we'll make sure it gets captured in a future edition. See you in a month!