Implement attributes detection on the client

[lttb]

• [x] detect properties on the client without react-dom
• [x] use whitelist on the server
• [ ] use browserstack for testing

import checkAttr from 'is-react-prop/checkAttr'

// the most efficient way

console.log(checkAttr('div', 'data-name')) // true
console.log(checkAttr('button', 'onClick')) // true
console.log(checkAttr('div', 'target')) // false
console.log(checkAttr(document.createElement('input'), 'onChange')) // true

import isReactProp from 'is-react-prop'

// it will add attributes list to the bundle

console.log(isReactProp('data-name')) // true
console.log(isReactProp('onClick')) // true
console.log(isReactProp('unknownProp')) // false

[kof]

is-react-prop project name doesn't fit, because it does much more

[kof]

cc @mxstbr @geelen @kentcdodds what do you think of this? What if we all had one package for this?

[lttb]

is-react-prop project name doesn't fit, because it does much more

@kof maybe is-html-attribute fits better?

[kof]

not really because you also have react specific stuff in there

[kentcdodds]

I'm planning on eventually making the glamorous solution totally tree-shakeable... 🤔

[kof]

I'm planning on eventually making the glamorous solution totally tree-shakeable... 🤔

what does this mean in this particular case?

[kentcdodds]

By that I mean that I might use a package like this, but only at build-time. Similar to what we're doing here which results in all the exports at the bottom of this file.