You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After update my angular to 11 to 12, the build console input this warging:
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
where i include it? resolve.fallback: { "crypto": false } ??
The text was updated successfully, but these errors were encountered:
@ipodjms AFAICT part of the issue with Webpack is indeed this library, so upgrading to v4.1.1 will definitely help.
But another part involved in my case was web3 library which also caused the compilation to fail due to the same error. For that I had to follow the steps described here to be able to compile/serve my app: https://github.com/ChainSafe/web3.js#web3-and-angular
Helo.
After update my angular to 11 to 12, the build console input this warging:
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }
where i include it? resolve.fallback: { "crypto": false } ??
The text was updated successfully, but these errors were encountered: