Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps-dev): bump react-docgen from 5.4.3 to 7.0.1 #566

Closed

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Dec 1, 2023

Bumps react-docgen from 5.4.3 to 7.0.1.

Release notes

Sourced from react-docgen's releases.

[email protected]

Patch Changes

[email protected]

Major Changes

  • #846 82154c3 Thanks @​danez! - 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:

    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:

    const type = getTypeFromReactComponent(path)
    -if (type) {
    +if (type.length > 0) {
    // do smth
    }

  • #848 dda8915 Thanks @​danez! - Drop support for Node.js version 14.

    The minimum supported version is now 16.14.0

  • #846 62e692f Thanks @​danez! - resolveToValue will not resolve to ImportDeclaration anymore but instead to one of the possible specifiers (ImportSpecifier, ImportDefaultSpecifier or ImportNamespaceSpecifier).

... (truncated)

Changelog

Sourced from react-docgen's changelog.

7.0.1

Patch Changes

7.0.0

Major Changes

  • #846 82154c3 Thanks @​danez! - 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:

    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:

    const type = getTypeFromReactComponent(path)
    -if (type) {
    +if (type.length > 0) {
    // do smth
    }

  • #848 dda8915 Thanks @​danez! - Drop support for Node.js version 14.

    The minimum supported version is now 16.14.0

  • #846 62e692f Thanks @​danez! - resolveToValue will not resolve

... (truncated)

Commits
  • 9994b2e Packages ready to publish (#871)
  • 2b51bbd fix(deps): update dependency @​types/doctrine to ^0.0.9 (#870)
  • de7b230 Packages ready to publish (#847)
  • 40ebb00 Support TypeScript builtin prop types (#862)
  • 74b6680 fix(deps): update dependency @​types/doctrine to ^0.0.8 (#861)
  • 3be404e Fix detection of ESM imports
  • 6312f2f fix(deps): update dependency @​types/doctrine to ^0.0.7
  • dda8915 Drop Node.js 14
  • 0a8882d fix linting
  • c01d1a0 Fix detecting super class in react class components
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [react-docgen](https://github.com/reactjs/react-docgen/tree/HEAD/packages/react-docgen) from 5.4.3 to 7.0.1.
- [Release notes](https://github.com/reactjs/react-docgen/releases)
- [Changelog](https://github.com/reactjs/react-docgen/blob/main/packages/react-docgen/CHANGELOG.md)
- [Commits](https://github.com/reactjs/react-docgen/commits/[email protected]/packages/react-docgen)

---
updated-dependencies:
- dependency-name: react-docgen
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Copy link
Author

dependabot bot commented on behalf of github Dec 1, 2023

The following labels could not be found: 🤖 dependabot 🤖.

Copy link

stale bot commented Mar 13, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Mar 13, 2024
Copy link
Author

dependabot bot commented on behalf of github Apr 1, 2024

Superseded by #596.

@dependabot dependabot bot closed this Apr 1, 2024
@dependabot dependabot bot deleted the dependabot-npm_and_yarn-react-docgen-7.0.1 branch April 1, 2024 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants