webpack: lots of new webpack errors?

Recently did a clean npm install of webpack, and when we try and run our build (via gulp) we’re getting a whole bunch of errors (seemingly originating in crypto-browserify - which had a new release last night). Any ideas?

ERROR in (webpack)/~/node-libs-browser/~/crypto-browserify/~/diffie-hellman/primes.json
Module parse failed: /PROJECT/node_modules/webpack/node_modules/node-libs-browser/node_modules/crypto-browserify/node_modules/diffie-hellman/primes.json Line 2: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
|     "modp1": {
|         "gen": "02",
|         "prime": "ffffffffffffffffc90fdaa22168c234c4c6628b80dc1cd129024e088a67cc74020bbea63b139b22514a08798e3404ddef9519b3cd3a431b302b0a6df25f14374fe1356d6d51c245e485b576625e7ec6f44c42e9a63a3620ffffffffffffffff"
 @ (webpack)/~/node-libs-browser/~/crypto-browserify/~/diffie-hellman/inject.js 1:13-37

ERROR in (webpack)/~/node-libs-browser/~/crypto-browserify/~/browserify-sign/aesid.json
Module parse failed: /PROJECT/node_modules/webpack/node_modules/node-libs-browser/node_modules/crypto-browserify/node_modules/browserify-sign/aesid.json Line 1: Unexpected token :
You may need an appropriate loader to handle this file type.
| {"2.16.840.1.101.3.4.1.1": "aes-128-ecb",
| "2.16.840.1.101.3.4.1.2": "aes-128-cbc",
| "2.16.840.1.101.3.4.1.3": "aes-128-ofb",
 @ (webpack)/~/node-libs-browser/~/crypto-browserify/~/browserify-sign/parseKeys.js 3:12-35

ERROR in (webpack)/~/node-libs-browser/~/crypto-browserify/~/browserify-sign/~/elliptic/package.json
Module parse failed: /PROJECT/node_modules/crypto-browserify/node_modules/browserify-sign/node_modules/elliptic/package.json Line 2: Unexpected token :
You may need an appropriate loader to handle this file type.
| {
|   "name": "elliptic",
|   "version": "0.15.14",
|   "description": "EC cryptography",
 @ (webpack)/~/node-libs-browser/~/crypto-browserify/~/browserify-sign/~/elliptic/lib/elliptic.js 3:19-45

ERROR in (webpack)/~/node-libs-browser/~/crypto-browserify/~/browserify-sign/~/elliptic/~/brorand/index.js
Module parse failed: /PROJECT/node_modules/webpack/node_modules/node-libs-browser/node_modules/crypto-browserify/node_modules/browserify-sign/node_modules/elliptic/node_modules/brorand/index.js Line 52: Illegal return statement
You may need an appropriate loader to handle this file type.
|       return res;
|     };
|     return;
|   }
|   Rand.prototype._rand = function _rand(n) {
 @ (webpack)/~/node-libs-browser/~/crypto-browserify/~/browserify-sign/~/elliptic/lib/elliptic.js 5:16-34

ERROR in (webpack)/~/node-libs-browser/~/crypto-browserify/~/diffie-hellman/~/miller-rabin/~/brorand/index.js
Module parse failed: /PROJECT/node_modules/webpack/node_modules/node-libs-browser/node_modules/crypto-browserify/node_modules/diffie-hellman/node_modules/miller-rabin/node_modules/brorand/index.js Line 52: Illegal return statement
You may need an appropriate loader to handle this file type.
|       return res;
|     };
|     return;
|   }
|   Rand.prototype._rand = function _rand(n) {
 @ (webpack)/~/node-libs-browser/~/crypto-browserify/~/diffie-hellman/~/miller-rabin/lib/mr.js 2:14-32

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Comments: 22 (5 by maintainers)

Most upvoted comments

same for beta.6

It’s required to use the json-loader for json files.

This issue is closed but still happening with webpack@2.1.0-beta.4.

Including json-loader or using shrinkwrap is nice workaround, but it doesn’t feel like final solution to me. Is there any other issue/PR to track this?

Thanks