stoically

Nice work on HTTPZ - and thanks for recommending Temporary Containers. :) Just a quick thought that came to mind while reading this: the web is moving to https-only anyway...

One way to test completely in Node without exporting the system under test using module.exports is to assign `browser` on `global`, then `require` the production code and finally wait until...

Until `sinon-chrome` is updated, you could look into my [`webextensions-api-mock`](https://github.com/stoically/webextensions-api-mock). Reason for building was that I wanted to be able to easily update to later WebExtensions schema versions and have...

I've encountered the same issue, it seems that it's not possible to use `sinon.match` if `sinon` isn't the very instance `sinon-chrome` is using internally.

Here's how one can reproduce: * Create folder `test` * Create folder `1` and folder `2` inside `test` * Inside `test/1`: `npm install sinon` * Inside `test/2`: `npm install sinon-chrome`...

I'd agree that's a good idea. This can be a really time-consuming edge-case, compared to an initial "you have to install sinon yourself"-hint to get it working (in a reliable...

https://docs.rs/error-stack in combination with `thiserror` looks promising for this task.

If possible it'd be nice to attach the `Node` to the error-stack report.

`syn` always expects a `syn::Error` to be returned from a parser struct / closure. So currently I don't see a way to expose a custom error to consumers. Only workaround...

Just to be sure: Your goal is to have code looking like e.g. ``` let key = "value"; ``` and have the element content be parsed as rust block?