-
-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Error with Storyshots, Jest and Canvas #6367
Comments
I was able to fix this by:
Eventually I would like to use the newer ( |
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am not sure if this bug lies within the realm of storybooks/storyshots itself, and it may actually need to be transferred to another project altogether, looking for some guidance as to where this belongs.
EDIT Links to outputs do not work (seems to be an issue with GitHub issues) so you will need to scroll down.
Describe the bug
I am trying to use the
@storybook/addon-storyshots
(^5.0
) with Vue and Vue Chart.js.In terms of using Vue Chart.js with the storybooks interface it all works as expected, however I am getting some issues related to
canvas
when trying to use the@storybook/addon-storyshots
with Jest.My
storybook.spec.js
is as follows (see more on my file structure here #5537):When I run
npm run test:unit
I get the following output (See below - Output 1).So based on that output I tried installing
canvas
(as well ascanvas-prebuilt
) withnpm
.After a bit of research I found this was related to
jsdom
see #1782 which recommended adding the following to my JestsetupFiles
:This helped reduce some of the errors and produced the following output (See below - Output-2).
Ultimately the test cases do run, however there are enormous amounts of error output related to
jsdom
andcanvas
. Also based on the error output I believe the issues with canvas are causing some issues with storyshot's i.eCannot read property 'length' of undefined
.To Reproduce
I am looking to create a minimal repo demonstrating this issue but first wanted to clarify whether or not this is in the scope of what storybook would consider theirs to fix?
Expected behavior
For the test case to only show errors related to storyshots finding changes in the rendered markup, to mute or remove all errors related to
jsdom
andcanvas
.System:
Additional context
Output 1
Output 2
The text was updated successfully, but these errors were encountered: