Would like to understand what's the reason for @storybook/test
to have testing-library pkgs built-in
#27528
Unanswered
csantos1113
asked this question in
General
Replies: 1 comment 2 replies
-
cc @yannbf You also had this problem with act warnings right? @csantos1113 We pre-bundle those packages for performance reasons. I will invrestigate what causes the act difference when prebundling. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to move away from https://github.com/storybookjs/testing-library to https://github.com/storybookjs/storybook/blob/v7.6.19/code/lib/test (I'm not ready to go up to 8.x)
And I thought it was going to be just find and replace; but it doesn't seem to be the case.
I've a lot of unit tests throwing
act()
warnings like:Triage
storybook/code/lib/test/package.json
Lines 71 to 74 in 0264a14
the
act()
warnings go away once I removed those 3 lines, built the package, and use that package.Why I think this is happening?
I believe this is because the version of
@testing-library/xxx
I have installed are different to the ones that are baked into@storybook/test
dist folder.noExternal
propNone of other storybook packages use this feature of baking dependencies into it. I wonder why
@storybook/test
is the exception?I see it was added in f42e9ef by @kasperpeulen but I've no clue as why
Note: I see that list still exists in
next
storybook/code/lib/test/package.json
Lines 71 to 74 in fdadc41
Appreciate any help 🙏
Beta Was this translation helpful? Give feedback.
All reactions