Improve util.deprecate

[silverwind]

As discussed in IRC recently with @Fishrock123 it would be nice if the deprecation messages contain a bit more info. Particulary I'd like to see

• filename:linenumber where it happens in userland code. I think this could be parsed off the stack through new Error().stack or similar, suggestions welcome.
• A prefix like (node) to identify where the messages come from.
• An flag like -print-all-deprecations to allow more than one print per deprecation to track down all places where it's happening.

[thefourtheye]

Why do we need the prefix? Can you include an example where it would be useful?

[silverwind]

Look at line 6 of https://gist.github.com/silverwind/a94589df8e3aae1907e1, do you think an outsider would know what to do based on that message, especially when they happen during something like npm install.

[thefourtheye]

Oh okay. You mean (request) ...? That would be good. About the line number and file name, what if the function is called more than once? Whenever user fixes one place he will get deprecation message for other places. Will that be okay?

[silverwind]

No, I mean a prefix that clearly identifies that the line was logged by node. For multiple prints: I want to keep the functionality to only prince once per function call, of course. Multiple messages should be opt-in through the flag.

[Fishrock123]

👍

[thefourtheye]

@silverwind What if other libraries start using util.deprecate? We cannot log (node) in that case, right?

[cjihrig]

Can't the existing --trace-deprecation flag be used to accomplish your first item? The second item seems a bit unnecessary. +1 to the third item.

[silverwind]

@thefourtheye I think the intention is to move to an internal module eventually, @vkurchatkin had it moved in a recent PR if I recall correctly.

[silverwind]

@cjihrig +1 on incorporating multiple prints into --trace-deprecation

[vkurchatkin]

@silverwind no, it is just a helper function. util.deprecate is untouched.

filename:linenumber where it happens in userland code. I think this could be parsed off the stack through new Error().stack or similar, suggestions welcome.

This is already available with --trace-deprecation

A prefix like (node) to identify where the messages come from.

This could be just a part of the message

An flag like -print-all-deprecations to allow more than one print per deprecation to track down all places where it's happening.

+0

[silverwind]

Right, I didn't realize we were exposing this knowingly in the public API, so it's probably best to include the (node) prefix in the messages itself.

[dougwilson]

People who want a public API should probably just use the depd module or similar.

[Fishrock123]

Right, but that doesn't really defer much from the fact that this already is public API.

The goal of what I was originally talking about was to better highlight spots where user code uses deprecated core APIs. However, I had forgotten about --trace-deprecation, which I think does that.