Release Notes
6.0.0-beta.5
Major Changes
-
d7a39af: Refactored
resolveComponentDefinitionutility.- Renamed to
findComponentDefinition - Removed named export
isComponentDefinition - The utility now does a lot more than previously, check out the commit to see the changes in detail.
- Renamed to
-
e956802: Remove match utility.
The utility can be replaced by babel helpers and is not needed anymore. Also using explicit checks like
path.isMemberExpression()is better for type safety and catching potential bugs. -
5215bab: Removed support for the
@extends React.Componentannotation on react class components.Instead you can use the new
@componentannotation. -
80e4c74: Renamed and migrated built-in resolvers to classes.
-
findAllComponentDefinitionswas renamed toFindAllDefinitionsResolverand is now a class.-const resolver = builtinResolvers.findAllComponentDefinitions +const resolver = new builtinResolvers.FindAllDefinitionsResolver() -
findAllExportedComponentDefinitionswas renamed toFindExportedDefinitionsResolverand is now a class.-const resolver = builtinResolvers.findAllExportedComponentDefinitions +const resolver = new builtinResolvers.FindExportedDefinitionsResolver() -
findExportedComponentDefinitionwas removed. UseFindExportedDefinitionsResolverwith thelimitoption instead.This is still the default resolver.
-const resolver = builtinResolvers.findExportedComponentDefinition +const resolver = new builtinResolvers.FindExportedDefinitionsResolver({ limit: 1 })
-
Minor Changes
-
80e4c74: Add the new ChainResolver which allows multiple resolvers to be chained.
import { builtinResolvers } from 'react-docgen'; const { ChainResolver } = builtinResolvers; const resolver = new ChainResolver([resolver1, resolver2], { chainingLogic: ChainResolver.Logic.ALL, // or ChainResolver.Logic.FIRST_FOUND, }); -
80e4c74: Allow resolvers to be classes in addition to functions.
import type { ResolverClass, ResolverFunction } from 'react-docgen'; // This was the only option until now const functionResolver: ResolverFunction = (file: FileState) => { //needs to return array of found components }; // This is the new class resolver class MyResolver implements ResolverClass { resolve(file: FileState) { //needs to return array of found components } } const classResolver = new MyResolver(); -
5215bab: Added a new resolver that finds annotated components. This resolver is also enabled by default.
To use this feature simply annotated a component with
@component.// @component class MyComponent {}
Patch Changes
- 8fe3dbf: Fix crash when using TypeScript mapped types
- ea25b16: Handle cyclic references in PropTypes
shape()andexact()methods. - 1aa0249: Handle
typeof import('...')andtypeof MyType.propertycorrectly in TypeScript - 050313d: Correctly add LICENSE file to published packages
- f6e4fe7: Update dependency strip-indent to v4
6.0.0-alpha.4
Major Changes
-
96d6e9e: Rename
flowTypeHandlertocodeTypeHandlerbecause it handles Flow and TypeScript -
96d6e9e: Simplify
resolveObjectValuesToArrayand remove type handling. None of the code that was handling types was actually used. -
caae6bf: The return values of
resolveObjectValuesToArrayare now in the order they are defined in the source code. -
96d6e9e: Migrate react-docgen to ES modules. Please read this (opens in a new tab)
-
3b28f6e: The CLI was removed from
react-docgeninto its own package@react-docgen/cli.Check out https://react-docgen.dev/cli (opens in a new tab) for the documentation.
-
96d6e9e: Main
parseAPI was changedThe main API changed and now includes only 2 arguments.
-parse(src, resolver, handlers, importer, options) +parse(src, { resolver, handlers, importer, ... }) -
96d6e9e: Renamed some of the main exports for clarity.
Renamed
handlerstobuiltinHandlersRenamedresolvertobuiltinResolversRenamedimporterstobuiltinImporters -
96d6e9e: Migrated to babel toolchain
This is one of the big changes in this new version of react-docgen. It made the code a lot more robust because there are now finally working TypeScript types for the ASTs.
Another benefit from this change that react-docgen is now a lot faster. 🚀 In some tests an improvement of nearly 50% was seen in comparison to version 5.
-
d4c27d4: Improve performance of file system importer.
The file system importer now also caches resolving of files in addition to parsing files. If the importer is used in an environment where files do change at runtime (like a watch command) then the caches will need to be cleared on every file change.
-
96d6e9e: Changed the minimum Node.js version to 14.17.0
Minor Changes
-
96d6e9e: Add support for
.ctsand.mtsextension when using typescript -
96d6e9e: Treat functions returning
React.Children.mapas components -
96d6e9e: Improve performance by creating all visitors only once
-
96d6e9e: Support all possible kinds of functions in the
displayNameHandler -
96d6e9e: Support all literal types in typescript
-
96d6e9e: Support flow qualified type names
-
96d6e9e: Support class and function declarations without identifier
-
96d6e9e: Support resolving of destructurings in
resolveToValue -
96d6e9e: Improve performance drastically by making changes to AST traversal
Visitors are now pre-exploded and are cached in the module scope instead of creating them on every call. This change brought the benchmark from 170ops/s to 225ops/sec
-
96d6e9e: Add codes to errors to be able to easily detect them
There is a new export
ERROR_CODESthat contains all possible error codes. The two errors that have codes right now are:MISSING_DEFINITION: No component found in fileMULTIPLE_DEFINITIONS: Multiple components found in one files
-
96d6e9e: Support handling
useImperativeHandlecorrectly
Patch Changes
- 96d6e9e: Handle
React.forwardRefcalls without a function - 96d6e9e: Handle some edge cases in resolveToValue
- 96d6e9e: Remove trailing commas and semicolons from raw values in the documentation
- 96d6e9e: Parse jsdoc comments for TypeScript structs
- 96d6e9e: Correctly handle ObjectProperties in
isReactComponentMethod - 96d6e9e: Add support for TSAsExpressions when trying to stringify expressions
6.0.0-alpha.3 (opens in a new tab) (2022-06-13)
Bug Fixes
- Correctly detect index access types in typescript (#400 (opens in a new tab)) (85ea6a5 (opens in a new tab))
- Correctly handle ObjectTypeSpreadProperty in object type annotations (#593 (opens in a new tab)) (395f338 (opens in a new tab))
- Fix typescript types for parsing (34c55ac (opens in a new tab))
- Fix wrong detection of forwardRef in combination with memo (#592 (opens in a new tab)) (ea9cbeb (opens in a new tab))
- Handle ObjectTypeSpreadProperties which are not resolvable (4b8b721 (opens in a new tab))
- Ignore methods in
Object.value()calls (4fc5b21 (opens in a new tab))
6.0.0-alpha.2 (opens in a new tab) (2022-04-04)
Bug Fixes
- Change folder name inside the npm package back to
dist. (5f3da8c (opens in a new tab)) There was no real reason to change this and happened during the TypeScript migration.
6.0.0-alpha.1 (2022-04-04)
Bug Fixes
- Fix for expressionTo with Spread and Methods (5f3da8c (opens in a new tab))
- Remove obsolete id check (66961d8 (opens in a new tab))
- Remove usage of ast-type builders (17c8a9c (opens in a new tab))
Features
- Migrate to TypeScript (7b35e6f (opens in a new tab))
- Remove building out of scope AST Nodes from resolveToValue (5bcf56c (opens in a new tab))
BREAKING CHANGES
resolveToValuewill not create aMemberExpressionfor targets ending in destructuring. It will now simply resolve to theIdentifierinside the destructuring. Use new helperisDestructuringAssignmentto further check this identifier.- The helpers
resolveObjectValuesToArrayandresolveObjectKeysToArrayreturn nowstring[]instead of aNodePath