Paket is a dependency manager for .NET and Mono projects, works well with NuGet packages and also allows to reference files directly from GitHub repositories.

In your projects.
Joined September 2014
I just released @PaketManager 8.0.0-alpha001 with experimental .NET 8 support. Please check it out.
7
22
2,307
Maximize your package management potential on #dotnet with 7 tips for getting the most out of @PaketManager in this week's blog post. Enjoy! #packagemanagement #nuget #csharp #fsharp ##vbnet buff.ly/3JJ8Gse
1
8
12
1,933
Also yay for CPM evangelizing! Happy to see some of these features coming to NuGet. The single shared version concept was always one of my favorite parts of @PaketManager
1
2
Anyone interested in fixing 2 issues for @PaketManager? Seems a compony in switzerland is paying for that. #fsharp
2
8
4
Latest @PaketManager 6.0.0-beta11 comes with support for .NET 6 - thanks @zerolehero
4
3
14
well I disagree, I use VS every day and also manage to pop up a terminal and type in: dotnet paket install x dotnet paket restore dotnet paket update dotnet restore dotnet build you can hire anyone an teach them those commands in 5 minutes.
2
3
3
Latest @PaketManager alpha is now compatible with netcoreapp5.0
3
20
How nice! Klarna mentions @PaketManager in their docs!
2
9
Hi F# users, I recently started to use dependabot for watching my dependencies. It works really great for js packages. But currently it only watches nuget references in fsproj files. Someone interested in adding a Paket lock file crawler? github.com/dependabot/depend… #paket #fsharp
1
9
14
I've just released @IonideProject Paket plugin 2.0 - it adds support for .Net Core version of @PaketManager installed as either global tool, or local per repo tool. #fsharp #toolingAdventures
1
9
24
Morning everyone! A good way for you to start the day - learn about the latest performance improvements in @PaketManager . A great example of how the netcore ecosystem is helping independent OSS tools thrive compositional-it.com/news-bl… @nuget @dotnet
3
11
2
18
Got a PR immediately. Thanks to @chethusk. Now trying to get it through the door. github.com/fsprojects/Paket/…
Urgs. DotNet Core 3.1 packages are popping up on NuGet. Anyone wants to add moniker code for @PaketManager?
2
1
2
The latest version of @PaketManager is now working as local dotnet tool. #fsharp #csharp
3
7
1
62
Finally. My @PaketManager is doing package GC like crazy. #fsharp
2
3
21
Another Monday, another #fsharp blog post on scripting! This time @PathakAttack takes you through using @PaketManager to make scripting easier, and discusses how scripts and unit tests both have their place. Enjoy! compositional-it.com/blog/20…
6
7
Replying to @ChetHusk @JamesNK
Yes, and it’s the default behavior. Even for small C# apps I wouldn’t go back to nuget client, let alone for large solutions. So much easier life with paket for the last 3+ years for me
3
5
Replying to @sforkmann
.NET Pro Tip is to use @PaketManager. And I don't mean that as fighting talk but as firmly held belief. If you're creating more than demo, single-file, single-project applications, Paket is the right choice.
1
5
11