There are tools that can cover this.
You personally may not use X, but what about your team mates?
Team leads should tell team members to use automated tools for coding standards. This takes care of most of this.
Your team (of 1+) may not use X, but do you ever have to debug modules or plugins written with X?
The Node.js community has a way of dealing with non evented-friendly code. Programming as a whole would probably benefit from more things like this.
We can debate how much effort is involved firewalling your code from X. It obviously varies depending on what precisely X is and how popular X is, but you clearly have to do more than simply “ignore” it.
Well, this thread has brought me to the awareness that there is always going to be some effort in this regard. Whichever programming language is used makes no difference.
I'm curious, which tools can you use for this?
Pycharm and related IDEs have Lint style tools for Javascript, for example. If your needs aren't met by existing tools, you can also roll your own. Many Lint-style programs have ways of coding your own checks.
Without taking a personal stance on these features, I suggest that “You can ignore Language Feature X” is often a weak argument. If you feel X is harmful, not only must you ignore it, but you must consider all of the other developers, maintainers, and so forth who interact with your code.
You personally may not use X, but what about your team mates?
Your team (of 1+) may not use X, but do you ever have to debug modules or plugins written with X?
If you really think X is a terrible idea, it’s in your best interests to discourage its existence, not just ignore it :-)