Dependency manager
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 34/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- fsharp
- Domain
- tooling
Research direction
Reproduce the FSharpInteractive workflow from the issue, starting with the dotnet tool-manifest and Paket commands and the VSCode settings.json FSharp.fsiExtraParameters entry. Trace how FSharp.DependencyManager.Paket locates paket.exe; done means the something.fsx script resolves FParsec without manually copying paket.exe.
Written by the indexing model from the issue text.
Description
Description
Attempted to play with the new features in FSharpInteractive using the FSharp.DependencyManager.Paket, but encountered some issues. Was thinking that we should provide an easier experience for newcomers.
Repro steps
In a new folder:
dotnet new tool-manifest
dotnet tool install paket
dotnet paket init
dotnet paket add FSharp.DependencyManager.Paket
Changed the settings.json for VSCode to include
{
"FSharp.fsiExtraParameters": [
"--compilertool:c:/Users/Sorin/.nuget/packages/fsharp.dependencymanager.paket/6.0.0-alpha053/lib/netstandard2.0"
]
}
Then created something.fsx with the content:
#r "paket: nuget FParsec"
open FParsec
Expected behavior
The script to run in FSI without issues
Actual behavior
exception while resolving dependencies:
System.Exception: Paket was not found in 'd:\dev\fsharp\sandbox\mlnet' or a parent directory, or 'C:\Users\Sorin'. Please download the tool and place it in one of the locations.
Known workarounds
To manually copy paket.exe in a reachable location for the FSI. The problem with that is that on a tool version change most probably the tooling around FSI will not work properly anymore.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fsprojects/Paket
-
agentic-workflows automation repo-assist
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fsprojects/Paket#4411 ·
-
agentic-workflows automation repo-assist
Difficulty 1/5 Under an hour Newbie friendliness 82/100
fsprojects/Paket#4400 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fsprojects/Paket#4255 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
fsprojects/Paket#2321 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
fsprojects/Paket#4428 ·
All issues in fsprojects/Paket
Similar issues
-
comp/cron P2 sweeper:risk-automation type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#117792 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
bancolombia/sentinel#20 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
alunduil/woodland-generators#669 ·