Michael Bradley

@mikezentz unfortunately embark has dependencies that aren't compatible with NodeJS v12.x, though we'll be looking to fix that. For now, please use either the latest 10.x (currently 10.16.0) or the...

```shell nvm install v10.16.0 ```

There's a merged PR that makes it more clear what versions of NodeJS are supported but those changes aren't yet part of a released version of Embark: https://github.com/embark-framework/embark/pull/1639.

It's not possible to effectively test these changes because the `--coverage` option for `embark test` is presently broken (on `master`). A story has been created in Pivotal Tracker re: the...

We feel your pain. However, node-gyp is strictly required by several of our transitive dependencies, i.e. dependencies of our dependencies. This is a problem facing many libraries and frameworks in...

> the need for fast crypto [in JavaScript contexts] I'm generally agreed, as are some of the folks that work on [EthereumJS](https://github.com/ethereumjs/) libs and the maintainer of web3.js; and probably...

I agree with @PascalPrecht, changes look good but tests are failing. Note that PR #2384 is also only 1 commit ahead of `master` but tests for that branch all passed.

@shayanhabibi > See the [status task runner](github.com/status-im/nim-task-runner) for a functioning implementation... Make sure to use the [`impl/beta2`](https://github.com/status-im/nim-task-runner/tree/impl/beta2) branch of nim-task-runner to get the latest changes. There's a draft PR https://github.com/status-im/nim-task-runner/pull/11...

> do you have a stable repro? Yes. I'll give the steps to repro, and if it seems too hacky then I'll try to make a branch where the repro...

I'm experiencing this behavior as well.