Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dotnet tool install fable #99

Closed
goswinr opened this issue Jul 14, 2021 · 4 comments
Closed

dotnet tool install fable #99

goswinr opened this issue Jul 14, 2021 · 4 comments

Comments

@goswinr
Copy link
Contributor

goswinr commented Jul 14, 2021

Is there a reason why dotnet tool install fable is not mentioned in the docs?
Or did I not find it? e.g. on https://fable.io/docs/2-steps/setup.html ?
I only read about it here: https://fable.io/blog/Announcing-Nagareyama-4.html

@MangelMaxime
Copy link
Member

95% of the documentation has been written when Fable was in version 2.

When releasing Fable 3 we probably forget the "obvious command for us".

I think we should add it to the Start a new project page. What do you think ?

Example:

  1. dotnet new --install Fable.Template
  2. dotnet tool install fable
  3. dotnet new fable

@alfonsogarciacaro
Copy link
Member

It's tricky because we can say there are two approaches: the "raw" one which would be something like:

dotnet tool install fable
dotnet fable src

And the template/sample clone approach. For the second approach there are several options in the next page in the docs. In these cases there's usually already a .config/dotnet-tools.json including Fable so you just need to do dotnet tool restore and this is often done in the build script of the template/sample (btw I just noticed the Fable.Template wasn't doing that so I pushed a new version to fix it). In fact, running dotnet tool install fable will throw an error like the following if there's a version mismatch:

Cannot add package. Manifest file already contains version 3.2.8 of the package fable. Uninstall/install or edit manifest file .config\dotnet-tools.json to specify the new version 3.2.9.

BTW, I wouldn't add the dotnet tool install fable in the Setup page, as these are system requirements and we recommend to install Fable locally (per project) not globally (per system).

@goswinr
Copy link
Contributor Author

goswinr commented Jul 15, 2021

Thanks for your quick replies.
For me a global installation is ok. But I am just a fable beginner. 🤷‍♂️ I thought there could be an alternative start from scratch to the start from template section. (that is downloading 6000 files from npm to run "Hello, World!" )
@MangelMaxime I was actually just trying to test this https://twitter.com/mangelmaxime/status/1415016383167991817

@goswinr
Copy link
Contributor Author

goswinr commented May 14, 2024

it's all good and there now

@goswinr goswinr closed this as completed May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants