Adopting standard style means ranking the importance of community conventions higher than personal style, which does not make sense for 100% of projects and development cultures. At the same time, open source can be a hostile place for newbies. Setting up clear, automated contributor expectations makes a project healthier.
Be aware that one of the choices is no semicolons, which I don't believe is popular enough to be considered a "community convention". However, key contributors in the Node community do advocate dropping semicolons, so things seem to be moving that way.
This project uses eslint and contains the
.eslintrc file so you don't have to worry about it. In fact, the idea of settling on a standard style guide for a project is sensible and something that can be automated rather than left to the PR/code review stage.
If you use Object.getOwnPropertyDescriptor and Object.defineProperty then you might like Simon Blackwell's propertyinterceptor (GitHub: anywhichway/propertyinterceptor, License: MIT, npm: propertyinterceptor):
It adds the following methods:
You can also short circuit the interceptor chain by throwing an
Error object. If you like
defineProperty but dislike the boilerplate, then you might prefer Simon's API.