Update to crypto-browserify 3.11.0 in your 0.5.3 version

[edi9999]

The version 0.5.3 of node-libs-browser currently depends on :

"crypto-browserify": "^3.2.6",

Which it self depends on [email protected] which was unlicensed.
This poses a problem for any webpack users since webpack uses version 0.5.3 of node-libs-browser.

Can you please release a new 0.5.4 version with crypto-browseriify 3.11.0 ?

This way, all sub licenses of webpack are conform with the license of webpack it self.

[sl-church]

I second this request. I am trying to incorporate JWT signing in an app and 3.2.6 does not support signing while the latest version does. Currently I just install the latest version with npm and delete the version under node-libs-browser. This works but I have to do the deletion every time I install a package.

Thanks.

[terinjokes]

@sokra There's a handful of issues asking for a 0.5.4 release. Alternatively, is there a reason to not upgrade the dependency of Webpack v1 to node-libs-browser@^1.0.0?

[jhnns]

We will bump node-libs-browser to ^1.1.0 in webpack-1, see webpack/webpack#3355

[jhnns]

There was a hidden breaking change with crypto-browserify so that we couldn't upgrade it to the most recent version. However, this PR introduces the most recent versions without breaking change to webpack-1.