3 ms·
If that's the case, then why is CouchDB treating it as a security error, and "fixing" it in 1.2.0? Change of heart?
by jashkenas 15y ago
If that's the case, then why is CouchDB treating it as a security error, and "fixing" it in 1.2.0? Change of heart?
- daleharvey 15y agoCouchDB introduced new functionality that allows extra use cases, in particular it can now handle npms use case in a secure manner, just because it didnt handle npms use case before and npm decided to expose that information does not mean it was ever couch's problem.