René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Webpack Config is stripping out Crypto","articleBody":"1. OS?  \n   Mac OSX El Capitan\n2. Versions. \n   angular-cli: local (v1.0.0-beta.10, branch: webpack)  \n   node: 4.4.7  \n   os: darwin x64  \n3. Repro steps.\n   I've pulled down the Angular-cli project and am building it locally, so I am using the new webpack version. \n   The project that I am building uses Crypto libraries (via a dependency of a dependency ...).\n   When I was running `ng build` I was seeing the dependency built like this:\n\n```\n    /* WEBPACK VAR INJECTION */(function(Buffer) {'use strict';\n\n    var crypto = __webpack_require__(147);\n    var BufferUtil = __webpack_require__(21);\n    var $ = __webpack_require__(15);\n\n    var Hash = module.exports;\n\n    Hash.sha1 = function(buf) {\n      $.checkArgument(BufferUtil.isBuffer(buf));\n      return crypto.createHash('sha1').update(buf).digest();\n    };\n    ...\n```\n\nAnd then when I looked at module 147 (I.E. the crypto module) I was seeing nothing there:\n\n```\n/***/ },\n/* 147 */\n/***/ function(module, exports, __webpack_require__) {\n\n/***/ },\n```\n\nAfter a while of searching I took a look in the Angular-CLI code and saw that part of the webpack config (addon/ng2/models/webpack-build-common.ts) was this:\n\n```\nnode: {\n      global: 'window',\n      crypto: 'empty',\n      module: false,\n      clearImmediate: false,\n      setImmediate: false\n    }\n```\n\nWhen I remove `crypto: 'empty'` everything builds correctly with the crypto module getting pulled in.\n\nSo my question is, why have you specified that crypto should be empty? \nIs there any way to fix this more permanently? \n","author":{"url":"https://github.com/jmc265","@type":"Person","name":"jmc265"},"datePublished":"2016-08-04T10:42:26.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":73},"url":"https://github.com/1548/angular-cli/issues/1548"}