Module not found: Error: Can't resolve 'crypto-js/sha256'

[willsmillie]

I have a couple of projects implementing the Loopring SDK. Today I started seeing some new errors upon attempting to build/deploy new releases for both of my projects implementing the SDK. Any insights to resolve would be greatly appreciated!

(base) ❯ Loopring-token-gate-react-example (main) ✘ yarn build
yarn run v1.22.15
$ react-app-rewired build
Creating an optimized production build...
Failed to compile.

Module not found: Error: Can't resolve 'crypto-js/sha256' in '/Users/willsmillie/Git/Loopring-token-gate-react-example/node_modules/@loopring-web/loopring-sdk/dist'
Did you mean 'sha256.js'?
BREAKING CHANGE: The request 'crypto-js/sha256' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.


error Command failed with exit code 1.

For some additional context: I'm using react-app-rewired, and webpack.

The project can be found here: https://github.com/willsmillie/Loopring-token-gate-react-example

[willsmillie]

@johnloopring @windatang Looks like this specific issue started to pop up 3.3.42 perhaps with the introduction of Rollup.

I hope this helps. If there is anything I can do, please let me know!

❌ 3.4.14 (Module not found: Error: Can't resolve 'crypto-js/sha256') | BREAKING CHANGE: The request 'crypto-js/sha256' failed to resolve only because it was resolved as fully specified
❔ 3.4.13 (untested)
❔ 3.4.12 (untested)
❌ 3.4.11 (Module not found: Error: Can't resolve 'crypto-js/sha256') | BREAKING CHANGE: The request 'crypto-js/sha256' failed to resolve only because it was resolved as fully specified
❌ 3.3.43 (Module not found: Error: Can't resolve 'crypto-js/sha256') | BREAKING CHANGE: The request 'crypto-js/sha256' failed to resolve only because it was resolved as fully specified
❌ 3.3.42 (Module not found: Error: Can't resolve 'crypto-js/sha256') | BREAKING CHANGE: The request 'crypto-js/sha256' failed to resolve only because it was resolved as fully specified
❌ 3.3.41 (Module not found: Error: Can't resolve '@loopring-web/loopring-sdk' | No dist folder in the sdk in node_modules)
❌ 3.4.0 (Can't resolve 'http', 'https', 'zlib' in 'micro-ftch' | pollyfills)
❌ 3.3.32 (Can't resolve 'http', 'https', 'zlib' in 'micro-ftch' | pollyfills)
✅ 3.3.38
✅ 3.3.37
✅ 3.3.36
✅ 3.3.35
✅ 3.3.34
✅ 3.3.33