All of our providers expect to be invoked as `node path/to/provider ...provider_args`, but on Windows, we are invoking them as `node -e require(path/to/provider) ...provider_args`. This throws off the provider's argument processing and causes connections to the resource monitor to fail. Fixes #477, though I think that there is going to be another issue with dynamic resources. |
||
---|---|---|
.. | ||
nodejs | ||
proto | ||
README.md |