You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello guys,
I have tried to install semantic UI several times but It stucks at the following stage:
Creating src/theme.config (LESS config) C:\Users\miladild\semantic\src\theme.config
I have Unistalled Node and Installed it again but it did not worked
Is anyone can who can help me?
Testcase
RickyLin, fpstidston, gspbirel56, dfsmirnov, giraffe-tree and 25 more
I have Win 10 and had no problem here to install/update (my last update was few days ago).
For @miladild problem, it seems to be the first file to be created, right ?
Maybe your npm/yarn doesn't have access to this directory, did you try to create your project outside your "user's folder" ?
@etshy I checked it. This is not a problem with user's folder. :(
I dont think its a problem with access rights because files in /semantic are created successfully (even theme.config)
npm version : 6.1.0
Activity
nighthacker commentedon Nov 5, 2018
The same problem here. Windows 10.
It is not possible to install this package for weeks.
This is ridiculous.
etshy commentedon Nov 6, 2018
I have Win 10 and had no problem here to install/update (my last update was few days ago).
For @miladild problem, it seems to be the first file to be created, right ?
Maybe your npm/yarn doesn't have access to this directory, did you try to create your project outside your "user's folder" ?
nighthacker commentedon Nov 6, 2018
@etshy I checked it. This is not a problem with user's folder. :(
I dont think its a problem with access rights because files in /semantic are created successfully (even theme.config)
npm version : 6.1.0
UPDATE:
npm updated to 6.4.1. - bug still exists.
fpstidston commentedon Nov 6, 2018
I have the same problem as @nighthacker
Also 6.4.1
AndrewBoklashko commentedon Nov 6, 2018
Hi everyone
I had the same problem and I was able to resolve it by installing earlier NodeJS version.
I was on 10.13.0 and downgraded to 10.11.0.
nighthacker commentedon Nov 6, 2018
Hello @SSkovboiSS
unfortunately, downgrade to 10.11 does not help in my case.
enginhu commentedon Nov 7, 2018
I have the same problem. Will try now downgrade the nodejs version.
enginhu commentedon Nov 7, 2018
Downgrading 10.11.0 worked for me.
mjauernig commentedon Nov 14, 2018
Exactly the same here.
49 remaining items