Specs defining browser #APIs use a formal definition language (#WebIDL) which helps with writing and implementing these APIs. @tidoust, @dontcallmeDOM and @foolip are making it easier to re-use these definitions through a newly released NPM package:
npmjs.com/package/@webref/id… 🎉🎇
1
7
2
8
That NPM package collects #WebIDL definitions from across all specifications identified as "#browser specifications" in a #github maintained registry: github.com/w3c/browser-specs
1
3
Then, these specifications are crawled by reffy, a tool that ingest plenty of useful data: #WebIDL definitions, but also #CSS grammar definitions, list of terms defined in the specs, cross-links, etc. github.com/w3c/reffy
Feb 11, 2021 · 12:53 PM UTC
1
1
All of that data has been collected and made available in another #github repo github.com/w3c/webref/
1
2
NPM packages the IDL pieces, with more packages (e.g. for #CSS definitions) in the pipe
1
2
To learn more about these projects and how that data gets reused (e.g. to document browser compat data in @MozDevNet), watch the presentation given during #w3cTPAC last October: youtube.com/r9AXrFoFEg4 (slides at w3.org/2020/Talks/TPAC/uncon…)
1

