VersionControlService.Runtime.Node
0.2.1
dotnet add package VersionControlService.Runtime.Node --version 0.2.1
NuGet\Install-Package VersionControlService.Runtime.Node -Version 0.2.1
<PackageReference Include="VersionControlService.Runtime.Node" Version="0.2.1" />
<PackageVersion Include="VersionControlService.Runtime.Node" Version="0.2.1" />
<PackageReference Include="VersionControlService.Runtime.Node" />
paket add VersionControlService.Runtime.Node --version 0.2.1
#r "nuget: VersionControlService.Runtime.Node, 0.2.1"
#:package VersionControlService.Runtime.Node@0.2.1
#addin nuget:?package=VersionControlService.Runtime.Node&version=0.2.1
#tool nuget:?package=VersionControlService.Runtime.Node&version=0.2.1
Node/Fable runtime adapters (filesystem, process, cancellation) for VersionControlService providers.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Fable.Core (>= 5.2.0)
- VersionControlService.Abstractions (= 0.2.1)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on VersionControlService.Runtime.Node:
| Package | Downloads |
|---|---|
|
VersionControlService.Git
Git and Git LFS provider for VersionControlService workspace sessions. |
|
|
VersionControlService.LakeFs
lakeFS provider for VersionControlService: API client, local workspace index, and provider-owned workspace branches. |
|
|
VersionControlService
Provider-neutral version control workspace services for Fable and .NET consumers. |
GitHub repositories
This package is not used by any popular GitHub repositories.
### Fixed
- With `versioncontrolservice.lfs.materializelargeobjects` on, the Git provider's `Update` and `Synchronize` (without `PublishLocalRevisions`) also run `git lfs pull` when there is nothing to merge, that is when the workspace is up to date or only ahead. Before, the large objects were only downloaded after a merge, so a workspace cloned or switched without them stayed with pointers. A failed download is a partial success with the `retry_materialization` recovery, as after a merge.