-
Notifications
You must be signed in to change notification settings - Fork 6.9k
Bower Install Fails #392
Comments
maybe it's due to your operating system. I'm not a windows user, due to this, I would need to try to install angular seed on windows OS to understand this because in OSx it works. As your npm-debug.txt log states;
As a result, I will try to install angular seed project on Windows 8 OS and see if I get similar errors. |
Well seems that's not an issue. I have used the following
|
Unfortunately there is not enough info on the error log to debug this. It seems that |
I don't know if it will help, but make sure you check out the "Common Issues" section here. |
@gkalpak yes I have looked at the common issues. git protocols are not an issue for me as I use them in other areas. Not really sure what to do. It says that it is an invalid JSON at one point. |
What is the output if you run |
|
@davidtaylorjr, I mean if you run |
sudo chown -R $USER:$GROUP ~/.npm This should solve it |
I'm on Windows though...
…On Sun, Jan 29, 2017 at 5:43 AM Pawan Shetty ***@***.***> wrote:
sudo chown -R $USER:$GROUP ~/.npm
sudo chown -R $USER:$GROUP ~/.config
This should solve it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#392 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJ7DfdSD6Q69Qjom7DZdq6lq44In2enfks5rXG0zgaJpZM4LsckA>
.
|
@davidtaylorjr, still waiting for an answer to #392 (comment). |
I've decided to fork the repo and quit using bower and instead use NPM for all dependencies. |
👍 (BTW, there is a pending PR for moving the repo away from bower: #390) |
@gkalpak Very good. I did complete this already and got a successful build. You can see my fork at https://github.com/davidtaylorjr/angular-seed It compiles correctly. I had to change a few things since on NPM the HTML5 Boilerplate is not updated. |
Currently trying to run npm install on the angular-seed and it keeps failing with the following output:
The full log output is attached.
npm-debug.txt
The text was updated successfully, but these errors were encountered: