-
Notifications
You must be signed in to change notification settings - Fork 41
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
Cannot run addons-frontend on Windows 10 #13297
Comments
I'll try to fix that, thanks for reporting this issue |
Do you use WSL by chance? https://docs.microsoft.com/en-us/windows/wsl/install-win10 |
@M4trox so I just tried and installed WSL with ubuntu 18.04. I think this is the way to go nowadays. You need Node 10.x, which can be installed using a |
@willdurand thank you for taking your time. I do believe that Then, there was a Python-related error: While trying to run the project locally, I also experienced some error related to And, finally, it started to work! :) I started doing changes in React components. Then, I wanted to run tests. Typed
I tried to manually kill flow instances ( Edit: I've read |
It should be in the dependencies already. 🤔
ahm, maybe my Windows 10 had a working python setup already (although it should not be shared with the WSL). Weird. Did you use Ubuntu 18.04? I did not install from the Store but I saw the Store has different Ubuntu versions. I used this Ubuntu: https://aka.ms/wsl-ubuntu-1804
Yeah, Flow isn't always super nice... It happened to me on MacOS too. While it'd be nice to have Flow, I think you can do a lot of things without. There is nothing we can do, though 😞 Great to hear that it works! |
Describe the problem and steps to reproduce it:
I'm trying to run
addons-frontend
on Windows 10.How to reproduce:
yarn
into terminalyarn amo:dev
What happened?
Command
yarn amo:dev
failed with an error:What did you expect to happen?
addons-frontend
will run without errorsAnything else we should know?
I'm running
Windows 10
withnode
installed throughnvm
, versionv12.6.0
.The text was updated successfully, but these errors were encountered: