-
Notifications
You must be signed in to change notification settings - Fork 9
crypto dependency breaks react native #9
Comments
|
I'll have to check tomorrow, but I have a feeling, this could be a bit more complicated. See Please remove this module from npm |
The issue you linked to only complains about the npm name being used. Could you please see if feathers-offline-realtime works after If not, you can remove the A good and cross-platform hash function is needed to implement optimistic mutation while disconnected. |
What I was trying to point out with that link is, that this module is not a replacement/polyfill for the native node module. Installing |
I am not looking for a pollyfill for the native Node module. I just want a SHA1 hash. I am still unclear from your answer if you did try the npm cypto module or not. This repo will need a cross-platform SHA1 hash within days, so I'd be grateful if you tried |
Ok, sorry. I did try and it did not work. |
Could brix/crypto-js be a solution? Haven't used it yet, but it seems to work with react native too. |
i should have been explicit that i won't be able to type with more than 1 finger for 5 days or more. perhaps you can try in the right folder if you didn't for knowledge sake. i'll look at your suggestion. thanks. |
i may be wrong, but as far as i can see brix/crypto-js creates and depends on global variables. i hope there's something that follows node standards better and has a good number of github stars. the error issue you mention getting mentions using |
this repo states it works on node & browser. a feathere core member has used in in react native. |
I expect this is fixed with #11 . It'll be published as 0.1.2. |
Perfect, works like a charm! |
With feathers-offline-realtime version 0.1.1 the crypto node module was added as a dependency, what breaks react native compatibility. The result is more or less this error.
Version 0.1.0 works fine with React Native.
The text was updated successfully, but these errors were encountered: