|
1 | 1 | # Release Notes |
2 | 2 |
|
| 3 | +## 8.0.1 |
| 4 | + |
| 5 | +### Patch Changes |
| 6 | + |
| 7 | +- [#1009](https://github.com/reactjs/react-docgen/pull/1009) |
| 8 | + [`4c7dd9d`](https://github.com/reactjs/react-docgen/commit/4c7dd9d12ffdb3ac1d6f9663124cc43ec7fabb08) |
| 9 | + Thanks [@danez](https://github.com/danez)! - Do not fail on new VoidPattern |
| 10 | + type |
| 11 | + |
3 | 12 | ## 8.0.0 |
4 | 13 |
|
5 | 14 | ### Major Changes |
|
10 | 19 | 18, 19 and 21. |
11 | 20 |
|
12 | 21 | With this `react-docgen` version Node.js support is: |
13 | | - |
14 | 22 | - Node.js 20.9.0 or newer 20.x versions |
15 | 23 | - Node.js 22.0.0 or any newer version |
16 | 24 |
|
|
221 | 229 | [`d7a39af`](https://github.com/reactjs/react-docgen/commit/d7a39af7162c312daba2be428613cb378cce0727) |
222 | 230 | Thanks [@danez](https://github.com/danez)! - Refactored |
223 | 231 | `resolveComponentDefinition` utility. |
224 | | - |
225 | 232 | - Renamed to `findComponentDefinition` |
226 | 233 | - Removed named export `isComponentDefinition` |
227 | 234 | - The utility now does a lot more than previously, check out the commit to see |
|
266 | 273 | - [`96d6e9e`](https://github.com/reactjs/react-docgen/commit/96d6e9e6003b92604781553f6910812c74c18dad) |
267 | 274 | Thanks [@danez](https://github.com/danez)! - The main `parse` API had some |
268 | 275 | breaking changes. |
269 | | - |
270 | 276 | - The arguments were changed from previously 5 to just 2. The following diff |
271 | 277 | illustrates how to migrate: |
272 | 278 |
|
|
304 | 310 | [`80e4c74`](https://github.com/reactjs/react-docgen/commit/80e4c747c19d80081c162118f9c7110916fc27a0) |
305 | 311 | Thanks [@danez](https://github.com/danez)! - Renamed and migrated built-in |
306 | 312 | resolvers to classes. |
307 | | - |
308 | 313 | - `findAllComponentDefinitions` was renamed to `FindAllDefinitionsResolver` |
309 | 314 | and is now a class. |
310 | 315 |
|
|
454 | 459 |
|
455 | 460 | There is a new export `ERROR_CODES` that contains all possible error codes. |
456 | 461 | The two errors that have codes right now are: |
457 | | - |
458 | 462 | - `MISSING_DEFINITION`: No component found in a file |
459 | 463 | - `MULTIPLE_DEFINITIONS`: Multiple components found in one file |
460 | 464 |
|
|
627 | 631 | ### Major Changes |
628 | 632 |
|
629 | 633 | - d7a39af: Refactored `resolveComponentDefinition` utility. |
630 | | - |
631 | 634 | - Renamed to `findComponentDefinition` |
632 | 635 | - Removed named export `isComponentDefinition` |
633 | 636 | - The utility now does a lot more than previously, check out the commit to see |
|
645 | 648 | Instead you can use the new `@component` annotation. |
646 | 649 |
|
647 | 650 | - 80e4c74: Renamed and migrated built-in resolvers to classes. |
648 | | - |
649 | 651 | - `findAllComponentDefinitions` was renamed to `FindAllDefinitionsResolver` |
650 | 652 | and is now a class. |
651 | 653 |
|
|
796 | 798 |
|
797 | 799 | There is a new export `ERROR_CODES` that contains all possible error codes. |
798 | 800 | The two errors that have codes right now are: |
799 | | - |
800 | 801 | - `MISSING_DEFINITION`: No component found in file |
801 | 802 | - `MULTIPLE_DEFINITIONS`: Multiple components found in one files |
802 | 803 |
|
|
0 commit comments