-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18
-
None
-
None
-
False
-
We should remove the crypto-browserify as its in a single place in whole codebase. In addition the only function that we use from this package is a hash generator that is replaceable with functions provided in browser native Crypto API and its digest function.
Steps to reproduce:
- Run console, debug the code of useUserSettings.ts
- See that the contents of 'userUid' variable gets initialized as before the changes.
Current results:
- Our codebase uses crypto-browserify to generate hashes for usernames in the useUserSettings hook
Expected results:
- We should use the Crypto's 'digest' function instead.
- The crypto-browserify package should be removed from the dependencies.