[cowboyd]

In order to support the widest degree of rendering frameworks and design systems, we're going to be implementing a subset of DOM features. But what does it mean to implement that subset, and how do we know that the features we implemented are done properly?

It turns out that there is a very extensive test suite maintained by the good folks at the W3C to test compatibility with the web platform https://github.com/web-platform-tests/wpt Including the DOM, and that we can use this to incrementally validate our own implementation.

This extracts a subset of the WPT (web platform tests) that don't pre-suppose a browser rendering engine, and allows us to declare a feature as either supported or unsupported. If it is declared as supported, then that test will be run against our DOM in CI, if not, then that test is not even part of our test suite.

For sanity checking, the test suite is also runnable in the browser via playwright, but this is only to validate that the test suite itself is valid.

This should allow us to add features to our DOM with complete confidence that we have met the bar.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​vitest/​expect@​5.0.5
	vite@​8.0.16 ⏵ 8.3.5		+21	+1
	@​standard-schema/​spec@​1.1.0
	typescript@​6.0.3
	typebox@​1.4.3

View full report

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/bombshell-dev/ui/@clack/ui@49

commit: fdb9191