No executable found matching command "bower"
See original GitHub issueSteps to reproduce
Create new ASP.NET Core Web Application. Try to publish from cmd/powershel with “dotnet publish”. After this i got such error: No executable found matching command “bower”.
How can i fix this?
Environment data
dotnet --info
output:
.NET Command Line Tools (1.0.0-preview2-002900)
Product Information: Version: 1.0.0-preview2-002900 Commit SHA-1 hash: f4ceb1f213
Runtime Environment: OS Name: Windows OS Version: 10.0.10586 OS Platform: Windows RID: win10-x64
Issue Analytics
- State:
- Created 7 years ago
- Comments:9
Top Results From Across the Web
No executable found matching command "bower" #6278
Create new ASP.NET Core Web Application. Try to publish from cmd/powershel with "dotnet publish". After this i got such error: No executable ......
Read more >No executable found matching command "bower"
I have solved the problem. need to install bower and gulp as a global packages. npm install -g bower. npm install -g gulp....
Read more >How to resolve no executable found matching command ...
I found this with a google search (google is free, BTW) Asd the following packages to my project.json: Under dependencies: "Microsoft.
Read more >Solving bower and bundling errors in imported ASP.NET ...
The most popular errors you get are these: “bower install” exited with code 9009; no executable found matching command “dotnet-bundle” ...
Read more >dotnet publish command returns npm error - Selfelected
Then you might get. No executable found matching command “bower”. which means that Bower is missing.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@emrahtokalak i solved the problem. need to install bower and gulp(if you use it) as a global packages
npm install -g bower
npm install -g gulp
@valamelkor I feel your pain. I am trying to get dotnet publish to work on a TeamCity build server. The problem with @GonzRu solution is that npm installs bower to your personal AppData directory, which is a terrible idea for a build server. Try this instead on your build server box (and agents!):
mkdir c:\npm
npm install bower -g --prefix c:\npm
You may want to install gulp while you are at it.