This will eventually contain all the WebIDL-generated bindings to Web APIs.

This is necessary for the WebIDL frontend, which can't translate many WebIDL
constructs into equivalent wasm-bindgen AST things yet. It lets us make
incremental progress: we can generate bindings to methods we can support right
now even though there might be methods on the same interface that we can't
support yet.

It was only `pub` so that we could test it, but we ended up moving towards
integration tests rather than unit tests that assert particular ASTs are parsed
from WebIDL files.

Instead of going into an infinite loop, detect when webpack-dev-server fails to
start up and early exit the test.

Instead of only a relative path.

This helps for debugging failing WebIDL-related tests.

Still need to fix and finish the test.

That way if we don't fill it in the error message doesn't look quite so bizarre

Otherwise we don't see any output!

Make sure these are looked up in the git project root rather than the crate root

This was meant for debugging and is otherwise pretty noisy

…ral)]`

Fixes rustwasm#432

…urposes

Helps debug bad WebIDL bindings generation inside tests.

This helps when debugging things that need to become structural.

We only use it to serialize headless tests so that we don't try to bind the port
concurrently. Its OK to run another headless test if an earlier one panicked.

Allows dynamically casting values to `js::Object` and `js::Function`.

If we create bindings to a method that doesn't exist in this implementation,
then it shouldn't fail until if/when we actually try and invoke that missing
method.

And document all the cast/convert/check methods for js value.