Closed tubauwe closed 7 years ago
The problem seems not to be crypto-pouch, but changes of the build process made by me to solve another error. After solving this error on another way there's no problem with crypto-pouch. Sorry, I was a little bit to fast.
After using crypto-pouch about two month without a problem, I get an old error again. I seems to be the same as in #40.
It came up after deleting the folder _nodemodules inside my project and using npm install to get all my dependencies again.
This is the message:
Is it possible, that the fixed error is coming up again after an update?
After removing crypto from my database there's no error.
I tried several combinations of pouchdb (6.0.7 and 6.1.0) and crypto-pouch (3.1.0 and 3.1.1). But the result is always the same.
Can you help me again? Thanks in advance.