Sounds good to me. This looks like a good first issue, unless I'm wrong? (I added the label, if anyone things that's not a good first issue feel free to remove it).

I would like to take up this issue. Can someone guide me through it as I am a first time contributor and the codebase is huge.
CC @mmarchini

Gentle ping @mmarchini

Hey @bhumijgupta, sorry for the delay, I didn't check GitHub during the long weekend. Have you contributed to the project before? If you haven't, I suggest starting by cloning the repository and making sure you can build it. Instructions to build are available in https://www.github.com/nodejs/node/tree/master/BUILDING.md.

@mmarchini I've cloned the repository and built the source code. Willing to take up the issue if @bhumijgupta is not working on it.

@preyunk I am working on the issue, although it may take some time for me to land a PR since the codebase and the tests affected by the changes are more in number

I'm generally -1 on displaying the stack traces by default. Warnings can already be very noisy, particularly deprecation warnings. Making them more noisy likely isn't going to be received well by most users.

Warnings can already be very noisy, particularly deprecation warnings.

Then maybe let's deprecate it and hard reject?