is-class-component
Version:
Determine if something is a React class component
63 lines (43 loc) • 2.66 kB
Markdown
[](https://www.npmjs.com/package/is-class-component)
[](http://travis-ci.org/overlookmotel/is-class-component)
[](https://david-dm.org/overlookmotel/is-class-component)
[](https://david-dm.org/overlookmotel/is-class-component)
[](https://greenkeeper.io/)
[](https://coveralls.io/r/overlookmotel/is-class-component)
# Determine if something is a React class component
## Usage
```js
import React from 'react';
import isClassComponent from 'is-class-component';
class Hello extends React.Component {
render() {
return <div>Hello!</div>;
}
}
class PureHello extends React.PureComponent {
render() {
return <div>Hello!</div>;
}
}
function FunctionalHello() {
return <div>Hello!</div>;
}
isClassComponent( Hello ) // -> true
isClassComponent( PureHello ) // -> true
isClassComponent( FunctionalHello ) // -> false
```
## Versioning
This module follows [semver](https://semver.org/). Breaking changes will only be made in major version updates.
All active NodeJS release lines are supported (v10+ at time of writing). After a release line of NodeJS reaches end of life according to [Node's LTS schedule](https://nodejs.org/en/about/releases/), support for that version of Node may be dropped at any time, and this will not be considered a breaking change. Dropping support for a Node version will be made in a minor version update (e.g. 1.2.0 to 1.3.0). If you are using a Node version which is approaching end of life, pin your dependency of this module to patch updates only using tilde (`~`) e.g. `~1.2.3` to avoid breakages.
## Tests
Use `npm test` to run the tests. Use `npm run cover` to check coverage.
## Changelog
See [changelog.md](https://github.com/overlookmotel/is-class-component/blob/master/changelog.md)
## Issues
If you discover a bug, please raise an issue on Github. https://github.com/overlookmotel/is-class-component/issues
## Contribution
Pull requests are very welcome. Please:
* ensure all tests pass before submitting PR
* add tests for new features
* document new functionality/API additions in README
* do not add an entry to Changelog (Changelog is created when cutting releases)