Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

better deprecation message UX #190

Closed
jonathanong opened this issue Dec 21, 2014 · 2 comments
Closed

better deprecation message UX #190

jonathanong opened this issue Dec 21, 2014 · 2 comments

Comments

@jonathanong
Copy link
Contributor

when a method is deprecated, it would be nice to show where it is being called so that devs know where to change it as well as which module author to blame. this would allow making breaking changes to be much easier in the future. this idea has helped express users upgrade through breaking changes seamlessly.

See: https://github.com/dougwilson/nodejs-depd

@bnoordhuis
Copy link
Member

It already works like that, only it wasn't documented until now (but see #191.)

bnoordhuis added a commit that referenced this issue Dec 30, 2014
Document the --trace-deprecation flag and the `process` properties that
affect util.deprecate().

Fixes: #190
PR-URL: #191
Reviewed-By: Jonathan Ong <me@jongleberry.com>
@bnoordhuis
Copy link
Member

Closing because of commit 8b04161. If you want to implement your suggestion from #191, cc me on the PR and I'll review it. Cheers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants