Skip to content
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

npm ci stop(emojione) #14

Closed
jbshin-gemiso opened this issue Jul 15, 2022 · 5 comments
Closed

npm ci stop(emojione) #14

jbshin-gemiso opened this issue Jul 15, 2022 · 5 comments

Comments

@jbshin-gemiso
Copy link

hello.

Thanks for making the mozilla hubs installation tutorial.
I ran into a problem during installation following your guide.
I've searched and searched for the cause, but I can't find a solution.
I want to get help.

1.4 Hubs
Clone and install dependencies in progress
npm ci hangs while running.
No matter how many times I try, the same emojione freezes.

I attach a screenshot below.

2022-07-15 112926

After npm ci failed, I tried npm install , but it still fails. in the same section.

The failure section is attached to the screenshot above.

I am using WSL2 on Windows 10 operating system.
I am using Ubuntu 20.04.4 LTS version.

Nodejs version is 10.19.0.
elixir version is 1.12.3-otp-23 .
erlang version is 23.2.1 .

Everything else was installed according to the procedure you gave.

Any help would be appreciated.
have a good day.

@albirrkarim
Copy link
Owner

How long it stuck on emojione ? in minute / hour ?

tell me your hardware (CPU& RAM) and your internet speed

@jbshin-gemiso
Copy link
Author

jbshin-gemiso commented Jul 18, 2022

I'm stuck on emojione forever.
I am in a situation where I have to abort the installation.

My PC specs requested are
CPU: intel i7-7700 3.60ghz
RAM: 64GB
internet : 100Mbps

@jbshin-gemiso
Copy link
Author

The problem seems to have been resolved.

I updated the versions of 'npm' and 'nodejs', downloaded hubs.git again, and installed it.
Another difference is, when the error occurred before, I was using linux installed on wsl2 using 'windows terminal'.

But I didn't use windows terminal this time. (using wsl2-ubuntu launcher directly)
I believe the latter would not have had much of an impact, and I believe the former solved the problem.

@albirrkarim
Copy link
Owner

So can we close this issue ?

@jbshin-gemiso
Copy link
Author

Yes, Sure.
Have a nice day :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants