Is your feature request related to a problem? Please describe.
After recent update I've started getting "ExperimentalWarning: queueMicrotask() is experimental." because of some of my dependencies (I don't even know which one and I don't have a clear way how to find it out).
This specific warning is useless to me since I can't/don't want to remove my dependencies. There are lots of discussion if this "queueMicrotask()" should/should not/will be at some time made not experimental.
I'm perfectly fine that it's experimental or not. I want just to acknowledge this one specific warning and don't look at it anymore.
I use "--trace-warnings" when testing so this and I need that flag, but, because of it "ExperimentalWarning: queueMicrotask()" is also followed by it's stack and thats really annoying.
Describe the solution you'd like
I'd like to have a command-line flag or a config file for node.js which allows disabling any warning by exact match or a regexp any would fit.
Describe alternatives you've considered
- I can interact with libraries support and they would probably argue that at some point of time this "ExperimentalWarning: queueMicrotask()" would not be experimental.
However, even after I wait for it, the progress would never stop. There will always be something new, experimental. And if you have "node_modules" with 100+ dependencies you'll likely catch this.
For now I see no way to disable "just this specific warning".
Is your feature request related to a problem? Please describe.
After recent update I've started getting "ExperimentalWarning: queueMicrotask() is experimental." because of some of my dependencies (I don't even know which one and I don't have a clear way how to find it out).
This specific warning is useless to me since I can't/don't want to remove my dependencies. There are lots of discussion if this "queueMicrotask()" should/should not/will be at some time made not experimental.
I'm perfectly fine that it's experimental or not. I want just to acknowledge this one specific warning and don't look at it anymore.
I use "--trace-warnings" when testing so this and I need that flag, but, because of it "ExperimentalWarning: queueMicrotask()" is also followed by it's stack and thats really annoying.
Describe the solution you'd like
I'd like to have a command-line flag or a config file for node.js which allows disabling any warning by exact match or a regexp any would fit.
Describe alternatives you've considered
However, even after I wait for it, the progress would never stop. There will always be something new, experimental. And if you have "node_modules" with 100+ dependencies you'll likely catch this.
For now I see no way to disable "just this specific warning".