You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, web_generator relies on the @webref/* JS libraries for parsing WebIDL definitions. This introduces a dependency on JS, introduces complexities in the build process, and slows down the development process.
The text was updated successfully, but these errors were encountered:
I'm trying to work on variadic arguments, and each run requires compilation. I'm looking to implement it myself. There are cons, like keeping it updated, but I don't think the IDL format and web specs change that much.
I'd be more worried we aren't handling corner cases correctly. I think reimplementing something like webidl2 is going to be quite a bit of effort and I would want it to be its own separate maintained package if we were to add it.
Note that we would still have to do something for MDN compat data even if we were to add this before we could move fully away from using any JS libraries.
Currently,
web_generator
relies on the@webref/*
JS libraries for parsing WebIDL definitions. This introduces a dependency onJS
, introduces complexities in the build process, and slows down the development process.The text was updated successfully, but these errors were encountered: