-
Notifications
You must be signed in to change notification settings - Fork 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
Build: Windows: Errors in fresh clone #27337
Comments
And this is the log from VSCode 0 info it worked if it ends with ok |
Hi @tofanelli Would you mind trying what is suggested here: https://stackoverflow.com/questions/49256190/how-to-fix-git-sh-setup-file-not-found-in-windows |
Hello @alisterscott didn't worked... both paths were added, machine restarted, and still same error... |
Ran a "npm run distclean" and the error is different now
And much more, I only copied a small portion... |
Even after saying its ready for fun =( |
So it's not loading even after showing that message? |
Nope... is not loading even after showing this message.... and using vagrant, i got stuck on "Compiling assets" for hours... |
@tofanelli: you're mentioning Vagrant, are you talking about https://github.com/Automattic/wp-calypso-bootstrap? |
Also, have you tried using WSL? |
@stephanethomas ... yes, exactly... sorry to not be clear... so, yes, i followed the steps, and the message "compiling assets" was stuck for like, 2 hours... so I gave up in this method and moved on... any idea what to do? |
@withinboredom unfortunately I'm using Windows 8.1 .64... there is no way to use WSL =( |
I see this too in Windows. Looks like it is related to npm/npm-lifecycle#20 which may not be in the version of node calypso currently supports. It was fixed about a month ago, so I gave node "engines": {
"node": "^10.11.0",
"npm": "^6.1.0"
},
and a |
Hey @withinboredom ... no luck man =( and still not loading anything =( .... any idea? |
I would try using regular powershell/cmd vs mingw64. As that usually has random cross compiled linux utils available to the shell. Node knows how to work in windows, and linux ... but mix them together and weird things happen sometimes. |
@withinboredom .... ok... i'm removing everything here now.... and starting again from scratch.... and I will use regular CMD.... lets see what I will get this time =) |
I've never heard of this particular issue, and I'm not sure how to fix it 😟. I've got a new version of Calypso Bootstrap coming in, you could give it another try. |
@stephanethomas looking at all these errors, I noticed something... did someone is actually using Calypso under Windows? Well, all these files are clearly not being loaded, and it might be for a fair and simple reason, the path is too long and Windows can only handle with up to 160 chars on its path... or am I saying non-sense here? I just opened all issues on the first page and noticed all OS they are using is iOS... but using vagrant I had another issues, so I think is not related to path length.
Well... now you just found someone who managed to create some unknown errors... if you need any other tests on a Windows Machine, tag me and lets try to solve this issue.... =) As soon you drop new version, please let me know so I will be able to try it out once again =) Cheers =) |
@tofanelli: the last error you had is actually similar to #27400, and should be easy to fix I'll see what I can do. |
I've created #27418 to address that issue. |
ok.. so this thread can be closed than... i guess... |
Steps to reproduce
What I expected
Full installation? =)
What happened instead
Error using Git Bash and Bash inside VSCode...
Browser / OS version
None yet / Windows 8.1 x64 Fully updated
Screenshot / Video
Context / Source
I just cloned the repo, added the address on my hosts file, started using "npm start" and got these both errors. There is nothing related to this error on WP KB...
What should I do now? =)
The text was updated successfully, but these errors were encountered: