Downgrading crypto-js to 3.1.9-1 solved this issue for me, it seems like this is the last stable version before this issue appeared!

npm install crypto-js@^3.1.9-1

then make sure your package.json looks like this:

"dependencies": {
  "crypto-js": "^3.1.9-1"
}

then

npm install