Support React.FC and companions

.changeset/cyan-ways-fry.md

@@ -0,0 +1,28 @@
+---
+'react-docgen': major
+---
+
+`getTypeFromReactComponent` now returns an array of paths to types instead of
+just one. This can appear when multiple type definitions are found for a
+component, for example:
+
+```ts
+const Component: React.FC<Props> = (props: { some: string }) => {};
+```
+
+In this example both the `Props` definition as well as `{ some: string }` are
+now found and used.
+
+Here is a simple diff to illustrate the change when using
+`getTypeFromReactComponent`:
+
+```diff
+
+const type = getTypeFromReactComponent(path)
+
+-if (type) {
++if (type.length > 0) {
+    // do smth
+}
+
+```

.changeset/eight-coats-tie.md

@@ -0,0 +1,6 @@
+---
+'react-docgen': patch
+---
+
+Fix detection of react class components when super class is imported via named
+import.

.changeset/four-teachers-tan.md

@@ -0,0 +1,20 @@
+---
+'react-docgen': major
+---
+
+`resolveToValue` will not resolve to `ImportDeclaration` anymore but instead to
+one of the possible specifiers (`ImportSpecifier`, `ImportDefaultSpecifier` or
+`ImportNamespaceSpecifier`). This gives better understanding to which specifier
+exactly `resolveToValue` did resolve a NodePath to.
+
+Here is a possible easy fix for this in a code snippet that uses
+`resolveToValue`
+
+```diff
+const resolved = resolveToValue(path);
+
+-if (resolved.isImportDeclaration()) {
++if (resolved.parentPath?.isImportDeclaration()) {
+    // do smth
+}
+```

.changeset/lazy-walls-swim.md

@@ -0,0 +1,6 @@
+---
+'react-docgen': patch
+---
+
+Remove unnecessary call to `resolveToValue` when trying to find props type from
+react components.

.changeset/sour-jeans-tell.md

@@ -0,0 +1,5 @@
+---
+'react-docgen': minor
+---
+
+Add support for React.FC in TypeScript