Hi, I started playing around with the project (great work by the way), and I found that I miss some of the creature comforts of other SPA development tools, mainly the CLI. It somehow takes me out of it to write dotnet blazor serve instead of a Blazor specific command blazor serve. (Think Angular cli ng serve etc.)
So, long story short, I started working on a blazor-cli. I'm definitely not the most qualified person to do this, but if anyone is interested, there it is :). Currently it is a bit of a mess and only allows blazor serve command. You can also check out the npm package
P.S.
Chose node because NPM should be somewhat familiar to SPA developers. Also cross platform.
kristapsstrals
All 2 comments
@SteveSandersonMS Now that global tools support is available in .NET Core 2.1, should we consider building the blazor CLI tool as a global tool? I think that would be our preferred approach instead of using npm and requiring a node dependency during development.
danroth27
on 18 Mar 2018
If it becomes common to need to run the Blazor CLI tool then yes, it would be nice to have a global tool that just runs whatever local version of the CLI tool you have installed in your project.
Currently there isn't yet any scenario where you need to run dotnet blazor ... directly. For example, instead of running dotnet blazor serve, it would be more normal to run dotnet run (which does the same thing).
So for now I don't think this is something we need to do anything about, but in the future it's quite possible that we will do.
Thanks for the idea, @struks93!
SteveSandersonMS
on 19 Mar 2018
Related issues
TanvirArjel
路
3Comments
UweKeim
路
3Comments
snebjorn
路
3Comments
Kevenvz
路
3Comments
FourLeafClover
路
3Comments
Most helpful comment
@SteveSandersonMS Now that global tools support is available in .NET Core 2.1, should we consider building the blazor CLI tool as a global tool? I think that would be our preferred approach instead of using npm and requiring a node dependency during development.