Warn about wrong Object.defineProperty usage

Please describe what the rule should do:

The rule should warn about faulty uses of Object.defineProperty and Object.defineProperties. It is not possible to combine a value property with a getter or setter or to combine the writable property with a getter or setter.

What category of rule is this? (place an “X” next to just one item)

[ ] Enforces code style [x] Warns about a potential error [ ] Suggests an alternate way of doing something [ ] Other (please specify:)

Provide 2-3 code examples that this rule will warn about:

'use strict';

const obj = {};

Object.defineProperty(obj, 'foo', {
  writable: true,
  get() {}
});

Object.defineProperty(obj, 'foo', {
  value: 'foo',
  get() {}
});

Why should this rule be included in ESLint (instead of a plugin)?

It provides an early feedback for a mistake. Especially if code has no tests, this might cause issues in some applications where an error is thrown at runtime.

[ljharb]

This should also then warn about the second argument to Object.create?

[eslint-deprecated[bot]]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to reach accepted status after 21 days tend to never be accepted, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.