Given the progress I've had in the short time I spent working on this, I believe this will reach a level of usability. But it depends on how much time

Search code, repositories, users, issues, pull requests...

submited by

Style Pass

2025-01-03 01:00:04

Given the progress I've had in the short time I spent working on this, I believe this will reach a level of usability. But it depends on how much time I will have for this.

You can help by sponsoring the project. If I could reach a level where I could work full-time on this, the Go community could have the most awesome testing tool at their disposal within a few months.

Software license (note: I currently distribute the source under the MIT license, but as this will most likely depend on v8go, I need to verify that the license is compatible).

This is still in early development, and the structure may still change. But I believe I am approaching a sensible code structure.

The main library is in a browser subfolder. This primarily to separate it from the code generator which is used to automatically generate parts of the code based on IDL specs. The browser and code generator bases do not have any inter-dependencies, and they have different sets of unrelated external dependencies.

The submodules under browser/ reflect the different standards, and the naming reflects the corresponding idl files. E.g., browser/dom/ will have types corresponding to the types specified in code-gen/webref/ed/idl/dom.idl. browser/html/ corresponds to html.idl, etc.