Closed RolfBabijn closed 8 years ago
What is the reasoning behind wanting a release around this change? Last I checked a missing repo field does not break any process.
That is right, it does not break anything, but it will result in cleaner logs and cleaner command line output. It is a bit like an old bicycle, it works perfectly fine when it makes an annoying noise when you brake, but it would be nice to use it without the noise.
We'll pull this in, but we'll make a release when we fix the clearly broken gear shift.
During
npm install
a warning is thrown that the repository field is missing. I've used the repository field that was added in the master branch. Would it be possible to create a maintenance release for this?