Description
In package.json, on line 28, mockfirebase declares a dependency on library "MD5": "~1.2.1".
This library has been deprecated as of recently.
The name of the package has been changed together with the version number, so 'MD5' is now changed to 'md5'.
In conclusion this means the dependency should be changed to "md5": "~2.0.0".
But obviously this might also mean the new md5 APIhas to be implemented (at least, for as far there are differences between md5 and MD5).
What's the problem with this
Running npm install on a project that uses mockfirebase will throw following error:
"No compatible version found: md5@'>=1.2.1 <1.3.0'"
...
"It was specified as a dependency of 'mockfirebase'"
Description In package.json, on line 28, mockfirebase declares a dependency on library "MD5": "~1.2.1". This library has been deprecated as of recently. The name of the package has been changed together with the version number, so 'MD5' is now changed to 'md5'. In conclusion this means the dependency should be changed to "md5": "~2.0.0". But obviously this might also mean the new md5 APIhas to be implemented (at least, for as far there are differences between md5 and MD5).
What's the problem with this Running
npm installon a project that uses mockfirebase will throw following error: "No compatible version found: md5@'>=1.2.1 <1.3.0'" ... "It was specified as a dependency of 'mockfirebase'"How to recreate
npm installReferences