Open ptbrowne opened 5 years ago
We should only remove cozy-harvest
from the registry and it will solves this issue. I tend to think we should not rename the package now, since we'll have to update all our apps. No need to create additional work.
OK, I started by deprecating cozy-harvest.
$ npm deprecate cozy-harvest "Cozy-harvest is deprecated. Please use cozy-harvest-lib"
I will delete the package in 1 month.
cozy-harvest and cozy-harvest-lib are both on the npm registry and it is confusing (I made a mistake and installed cozy-harvest instead of cozy-harvest-lib this morning). We should have only one package IMHO.