Answer the question
In order to leave comments, you need to log in
What is the problem when running BOWER?
I decided to simplify my life by putting a bower. I work with 2 computers (stationary and laptop). On the first one, everything started perfectly - it works. (node.js, npm and git were right there). On the laptop, everything went awry: it turns out that the person who worked on it some time ago removed git and installed gitnub, the rest of the equipment was the same as on the computer. In general, after chugging npm, this came out:
C:\Users\MaxLevs\AppData\Roaming\npm\bower -> C:\Users\MaxLevs\AppData\Roaming\n
pm\node_modules\bower\bin\bower
[email protected] C:\Users\MaxLevs\AppData \Roaming\npm\node_modules\bower
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] .0
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── bower-endpoint [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected])
├── [email protected]
├── [email protected] ([email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected],
[email protected])
├─ ─ [email protected] ([email protected], [email protected], [email protected]
.2.0, [email protected], [email protected])
├ ── [email protected] ([email protected], [email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected])
├── [email protected] 1.0.2 ([email protected], [email protected])
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected]
, [email protected])
├── [email protected] 6 ([email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected] .0,
[email protected], [email protected], [email protected], [email protected],
[email protected], [email protected], mime- [email protected], [email protected], [email protected], tough-coo
[email protected], [email protected], [email protected])
├── bower-registry- [email protected] ([email protected], [email protected], lru-ca
[email protected], [email protected], [email protected], [email protected])
├ ── [email protected] ([email protected])
├── [email protected]
├── [email protected] ([email protected], [email protected], latest-versio
[email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected]
.1.1, [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], os [email protected],
[email protected], [email protected], [email protected], [email protected])
Answer the question
In order to leave comments, you need to log in
It is not necessary to write the path to the bower itself, but there should be a path to the place where npm puts global modules. What will happen if you put, for example, grunt-cli?
Bower can also be naughty if git is not available globally (if set by default, then it only works in some kind of git bash).
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question