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

Update dependencies for React 19 type compatibility #30031

Open
wants to merge 10 commits into
base: next
Choose a base branch
from

Conversation

mrginglymus
Copy link

@mrginglymus mrginglymus commented Dec 11, 2024

Closes #30104

What I did

A number of bundled packages in storybook still use the deprecated global JSX namespace from React; this PR makes minor updates to those packages to bring in React 19 type-compatible versions.

There may be further issues with @storybook/blocks, but I'm having trouble building it (even on next). I'm on a limited dev environment as I only have access to a Windows and WSL dev environment, and storybook does not play nice with Windows...

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This pull request has been released as version 0.0.0-pr-30031-sha-5acb6e15. Try it out in a new sandbox by running npx [email protected] sandbox or in an existing project with npx [email protected] upgrade.

More information
Published version 0.0.0-pr-30031-sha-5acb6e15
Triggered by @yannbf
Repository mrginglymus/storybook
Branch r19-type-compat
Commit 5acb6e15
Datetime Sat Dec 14 09:32:09 UTC 2024 (1734168729)
Workflow run 12328745571

To request a new release of this pull request, mention the @storybookjs/core team.

core team members can create a new canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=30031

name before after diff z %
createSize 0 B 0 B 0 B - -
generateSize 77.8 MB 77.8 MB 0 B 2.27 0%
initSize 133 MB 133 MB -38.9 kB -0.74 0%
diffSize 55.3 MB 55.3 MB -38.9 kB -0.74 -0.1%
buildSize 7.19 MB 7.17 MB -17.3 kB -7.06 -0.2%
buildSbAddonsSize 1.85 MB 1.85 MB 500 B -1.04 0%
buildSbCommonSize 195 kB 195 kB 0 B - 0%
buildSbManagerSize 1.87 MB 1.86 MB -5.17 kB -8.83 -0.3%
buildSbPreviewSize 0 B 0 B 0 B - -
buildStaticSize 0 B 0 B 0 B - -
buildPrebuildSize 3.91 MB 3.9 MB -4.67 kB -2.77 -0.1%
buildPreviewSize 3.28 MB 3.26 MB -12.6 kB -Infinity -0.4%
testBuildSize 0 B 0 B 0 B - -
testBuildSbAddonsSize 0 B 0 B 0 B - -
testBuildSbCommonSize 0 B 0 B 0 B - -
testBuildSbManagerSize 0 B 0 B 0 B - -
testBuildSbPreviewSize 0 B 0 B 0 B - -
testBuildStaticSize 0 B 0 B 0 B - -
testBuildPrebuildSize 0 B 0 B 0 B - -
testBuildPreviewSize 0 B 0 B 0 B - -
name before after diff z %
createTime 7s 7s 16ms -0.63 0.2%
generateTime 19.7s 20.5s 836ms -0.03 4.1%
initTime 13.2s 14.1s 880ms -0.12 6.2%
buildTime 9.4s 8.4s -1s -18ms -0.73 -12%
testBuildTime 0ms 0ms 0ms - -
devPreviewResponsive 4.5s 6.4s 1.8s 1.42 🔺28.9%
devManagerResponsive 3.3s 4.5s 1.1s 1.46 🔺26.2%
devManagerHeaderVisible 558ms 694ms 136ms 0.44 19.6%
devManagerIndexVisible 569ms 762ms 193ms 0.7 25.3%
devStoryVisibleUncached 1.9s 1.6s -240ms -1.02 -14.2%
devStoryVisible 588ms 728ms 140ms 0.37 19.2%
devAutodocsVisible 534ms 590ms 56ms 0.2 9.5%
devMDXVisible 459ms 567ms 108ms 0.04 19%
buildManagerHeaderVisible 548ms 698ms 150ms 0.58 21.5%
buildManagerIndexVisible 687ms 795ms 108ms 0.56 13.6%
buildStoryVisible 536ms 668ms 132ms 0.52 19.8%
buildAutodocsVisible 427ms 517ms 90ms 0.12 17.4%
buildMDXVisible 423ms 574ms 151ms 0.94 26.3%

Greptile Summary

Updates dependencies and type definitions across multiple packages to ensure compatibility with React 19, particularly addressing the deprecated global JSX namespace.

  • Added patch to code/.yarn/patches/markdown-to-jsx-npm-7.7.1-6038885620.patch to use React.ReactNode instead of React.ReactChild
  • Updated React peer dependencies in code/lib/blocks/package.json to include React 19 beta
  • Modified code/renderers/react/src/types.ts to import JSX namespace directly from React
  • Updated emotion packages and @radix-ui/react-dialog in code/core/package.json for React 19 compatibility
  • Added 'as const' assertion in code/lib/blocks/src/blocks/mdx.tsx for type safety

💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!

@imjordanxd
Copy link

It would be EPIC if this could be pack-ported to Storybook v6 and v7 🚀

@mrginglymus
Copy link
Author

OK, I found the problem with building @storybook/blocks. I've updated markdown-to-jsx to its latest version, but even that doesn't fully support React 19 yet type-wise, so I've patched it to expedite getting storybook type-compatible, and will raise a PR over there soon.

@mrginglymus mrginglymus marked this pull request as ready for review December 14, 2024 09:31
@yannbf yannbf added the ci:merged Run the CI jobs that normally run when merged. label Dec 14, 2024
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

5 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

@yannbf
Copy link
Member

yannbf commented Dec 14, 2024

Thanks for your contribution @mrginglymus! I have started a canary release so you can test it out in a real scenario.

@imjordanxd unfortunately won't happen, it would be amazing if you could upgrade your project instead. There are a ton of incredible fixes and features we have shipped since Storybook 6/7, please consider upgrading if possible.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

5 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

Copy link

nx-cloud bot commented Dec 14, 2024

View your CI Pipeline Execution ↗ for commit dad7a7a.

Command Status Duration Result
nx run-many -t build --parallel=3 ✅ Succeeded 1m 36s View ↗

☁️ Nx Cloud last updated this comment at 2025-01-02 10:21:54 UTC

@storybook-pr-benchmarking
Copy link

storybook-pr-benchmarking bot commented Dec 14, 2024

Package Benchmarks

Commit: dad7a7a, ran on 2 January 2025 at 10:17:38 UTC

The following packages have significant changes to their size or dependencies:

@storybook/core

Before After Difference
Dependency count 50 50 0
Self size 21.45 MB 21.41 MB 🎉 -43 KB 🎉
Dependency size 14.37 MB 14.37 MB 0 B
Bundle Size Analyzer Link Link

storybook

Before After Difference
Dependency count 51 51 0
Self size 22 KB 22 KB 0 B
Dependency size 35.82 MB 35.77 MB 🎉 -43 KB 🎉
Bundle Size Analyzer Link Link

sb

Before After Difference
Dependency count 52 52 0
Self size 1 KB 1 KB 0 B
Dependency size 35.84 MB 35.79 MB 🎉 -43 KB 🎉
Bundle Size Analyzer Link Link

@storybook/cli

Before After Difference
Dependency count 393 393 0
Self size 496 KB 496 KB 0 B
Dependency size 77.72 MB 77.68 MB 🎉 -43 KB 🎉
Bundle Size Analyzer Link Link

@storybook/codemod

Before After Difference
Dependency count 273 273 0
Self size 612 KB 612 KB 0 B
Dependency size 67.62 MB 67.58 MB 🎉 -43 KB 🎉
Bundle Size Analyzer Link Link

create-storybook

Before After Difference
Dependency count 109 109 0
Self size 1.11 MB 1.11 MB 0 B
Dependency size 44.95 MB 44.91 MB 🎉 -43 KB 🎉
Bundle Size Analyzer Link Link

@mrginglymus
Copy link
Author

mrginglymus commented Dec 14, 2024

Thanks for your contribution @mrginglymus! I have started a canary release so you can test it out in a real scenario.

Thanks - my project now passes type checking and the storybook continues to build correctly using this canary release

@yannbf
Copy link
Member

yannbf commented Dec 16, 2024

Hey @mrginglymus thanks for getting back to us! We as a team feel like the markdown-to-jsx dep shouldn't be patched. Ideally the maintainers of markdown-to-jsx should make a release with the fix. Seems like the repo is quite active, I'm wondering if you got around to either reporting or making a PR to their repo?

@yannbf yannbf self-assigned this Dec 16, 2024
@mrginglymus
Copy link
Author

mrginglymus commented Dec 16, 2024

I'd be happy to, but my concern is around this comment: quantizor/markdown-to-jsx#435 (comment) where even type compatibility with react 18 appears to be something for the v8 release, currently only present as a WIP PR (quantizor/markdown-to-jsx#559).

I can re-raise the issue and see if they can be persuaded to drop type-compatibility with older React versions without a major version bump.

This is all nonsense (:

@mrginglymus
Copy link
Author

mrginglymus commented Dec 16, 2024

Actually, the change seems pretty trivial so hopefully it'll be ok.

edit: quantizor/markdown-to-jsx#643

@mrginglymus
Copy link
Author

@yannbf PR updated with the now fixed-at-source markdown-to-jsx

@mrginglymus mrginglymus requested a review from yannbf December 18, 2024 09:19
@devjiwonchoi
Copy link

FYI Closes #30104

@yannbf
Copy link
Member

yannbf commented Dec 27, 2024

@mrginglymus seems like some types are failing, can you check?

yarn task --task check --start-from=install --no-link --debug

@kasperpeulen can you assist if needed?

@yannbf yannbf assigned kasperpeulen and unassigned yannbf Dec 27, 2024
@yannbf yannbf requested a review from kasperpeulen December 27, 2024 09:48
@mrginglymus
Copy link
Author

mrginglymus commented Dec 27, 2024

Ah sorry, only just spotted those. There's some lovely weirdness where the checks are passing on Windows (except for svelte - https://cloud.nx.app/runs/nCgcPQNBdY).

Also, running with the --start-from flag is giving me an error:

TypeError: Cannot read properties of undefined (reading 'filter')
    at setUnready (...\storybook\scripts\task.ts:414:14)
    at run (...\storybook\scripts\task.ts:439:5)

on both windows and linux.

I'm stuck between not being able to build from an empty cache on windows, and the ts language service not seeming to work in WSL, so I can't offer much of a better fix than just throwing a few as const around.


Windows support might be aided by fixing these lines:

export * from '${join(upwards, downwards)}';
export type * from '${join(upwards, downwards)}';

to add a .replaceAll(path.sep, '/'), but I'm curious as to whether storybook have considered using typescript project references to simplify the build system and avoid the need for temporary stubs

edit: #30148 raised to enhance windows support

@mrginglymus
Copy link
Author

mrginglymus commented Dec 27, 2024

Hmm, it looks like all of these are caused by emotion-js/emotion#3164 .

The offending code looks like this:

const MyComponent = styled.xxx(() => ({
  ...
}));

ie, a styled component with no theme arg

I can see three options for fixing:

  1. Slap an as const on it:
const MyComponent = styled.xxx(() => ({
  ...
} as const));
  1. Remove the unecessary callback
const MyComponent = styled.xxx({
  ...
});
  1. Raise a bug with emotion for this regression (if it is one, which I think it is...)

@yannbf
Copy link
Member

yannbf commented Jan 2, 2025

Thank you so much for all of your findings @mrginglymus! About the check command, I gave you the wrong one, it shouldn't have the --start-from=install flag, sorry about that.

Regarding the issue, I fixed the styled components ones, and the check command should be passing now.

@mrginglymus
Copy link
Author

mrginglymus commented Jan 2, 2025

Thanks for the updates @yannbf! I'll look into those test failures now.

edit: passes on my machine 😕 - is there some known flakiness on those tests?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci:merged Run the CI jobs that normally run when merged. dependencies react
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: @storybook/react types is incompatible with @types/react@19 Cannot find namespace 'JSX'.
5 participants