-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[🐛 Bug]: Setup through CLI - npx wdio config --npm-tag latest! error #12633
Comments
@wswebcreation are you aware of any special requirements one would have to have installed on their machine? We should mention any hard requirements for Canvas. @juannavalonribas what Mac architecture are you using M1, M2 or M3? Can you try running the following: brew install pkg-config cairo pango libpng jpeg giflib librsvg pixman And then try again? |
Hello @christian-bromann I am using a mac Apple M1 with Sonoma 14.4.1 (sorry for not including this info previously) I installed the tools according to the command that you provided. I figure it out the problem. I was creating the project inside my wdio-visual-testing folder. I though that this won't cause problems cause during the wdio command the first options is ? A project named "wdio-visual-testing" was detected at "/Users/juan/Documents/wdio-visual-testing/wdio-visual-testing", but it seems that if you select to execute npm saying Y on the last step everything explodes because is on the first folder I just decline the install and navigate to the child folder which is named as the parent. so running Thanks! |
Have you checked the System Requirements and followed the steps there? As far as I can see it fails on the fallback to build canvas @christian-bromann , see the link to the requirements |
No @wswebcreation my bad, I was following your youtube video and just running the init command 😅. But after installing the requirements and do what I mentioned on my previous comment "cd to child folder" now is working. I would be nice to give to the CLI more control in order to install everything automatically avoiding human mistake such not install the requirements previously. Thanks for your support. |
Is |
Parent /wdio-visual-testing is just an empty folder and inside I runned the wdio init which creates another folder in this case named same as parent. I just played with different cases and doing the wdio init on Documents I have the same error if I say yes through the CLI. |
Can you explain what commands you entered in your terminal? |
Just I attach a video |
mhm 🤔 I have no issues creating a project as demonstrated in the video in my |
Can you try to run this: brew install pkg-config cairo pango libpng jpeg giflib librsvg pixman and rerun your installation? |
I did it before, that brew install works properly but the cli setup is giving the same error. I have on my .zshrc a private npm_token of my company.. 🤔 could be that? But recently I been creating projects with vite and another CLI's with success. |
Mhm 🤔 I am a bot out of ideas here. I've ran a workshop today where most people were able to install the visual package and the ones that weren't, were able to install it after calling the |
If installing the requirements does not work from my experience, the issue is the following. node-canvas can only be built using the legacy python 2.7.18. You can install pyenv, then install Python 2.7.18 and then set your shell to this version which (if you installed the requirements correctly) should work. To set the version in the shell use "pyenv shell 2.7.18" and then run the wdio setup like before. Let me know if this resolves the issue. |
Closing due to inactivity. |
Have you read the Contributing Guidelines on issues?
WebdriverIO Version
latest
Node.js Version
20.11.1
Mode
Standalone Mode
Which capabilities are you using?
No response
What happened?
I just want to setup a new project using the wdio visual service so I just follow the setup on the following video
https://www.youtube.com/watch?v=wQRGpWX3fsk&t=1s
I also tried with node 18 and I had the same ouput as node 20.11.1
What is your expected behavior?
Install the following dependencies should work correctly.
command: 'npm install @wdio/local-runner@latest @wdio/mocha-framework@latest @wdio/spec-reporter@latest wdio-wait-for @testing-library/webdriverio @wdio/visual-service ts-node @wdio/visual-service --save-dev'
How to reproduce the bug.
Run
npm init wdio@latest project-name
Select the following configuration
-❯◉ Chrome
Relevant log output
Code of Conduct
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: