bug: custom message doesn't apply about npm-deprecate HOT 6 CLOSED

Btw, I tried to create .npm-deprecaterc.json, and .npm-deprecaterc, but it still doesn't work.

from npm-deprecate.

@favna

from npm-deprecate.

@favna

I saw the issue 6 days ago when you made it. I just haven't had time to address it. Comes with having a full time job and getting burned out from coding.

from npm-deprecate.

@favna

I saw the issue 6 days ago when you made it. I just haven't had time to address it. Comes with having a full time job and getting burned out from coding.

Sorry for this, since I have automated deprecation, it deprecates every time I push a commit with the wrong message, so it was somewhat important to me to fix this issue.

from npm-deprecate.

It should be fixed in v1.0.6.

Anyway, I think you stress far too much about the message. From my experience, most people who use NPM don't read about a dependency being deprecated in the first place let alone the exact message for that deprecation.

from npm-deprecate.

Yeah but I'm a bit materialistic, thanks so much though.

from npm-deprecate.