| Crates.io | junction-verbatim |
| lib.rs | junction-verbatim |
| version | 1.3.1 |
| created_at | 2025-12-21 16:02:10.650443+00 |
| updated_at | 2026-01-18 09:36:35.718205+00 |
| description | DEPRECATED: Use upstream `junction` v1.4.1+ crate instead (verbatim prefix fix merged) |
| homepage | |
| repository | https://github.com/DK26/junction |
| max_upload_size | |
| id | 1998172 |
| size | 49,529 |
junction Crate InsteadThis crate is no longer needed. The verbatim prefix fix has been merged and published in the upstream junction crate.
Replace junction-verbatim with junction in your Cargo.toml:
# Old:
# junction-verbatim = "1.3.0"
# New:
junction = "1.4.1" # or latest version
The API is identical, so no code changes are required—just update your dependency and imports:
// Change from:
// use junction_verbatim::{create, delete, exists, get_target};
// To:
use junction::{create, delete, exists, get_target};
This was a fork of tesuji/junction with a fix for verbatim prefix handling.
Library for working with NTFS junctions.
As opposed to symlinks, junction does not require administrator privileges during creation. (However starting with Windows 10 Insiders build 14972, symlinks can be created without needing to elevate the console as administrator)^1.
Quoted from Computer Hope:
A junction, also called an NTFS junction point, is a feature of the NTFS file system. It is pointer to a directory on the local volume, similar to a symlink. It can be accessed through the Windows GUI in addition to the Windows command line. Junction points were first introduced with Windows 2000 and NTFS 3.0, and are supported in all subsequent versions of Windows.
This fork fixed an issue where junction::create() would silently fail when passed paths containing the Windows verbatim prefix (\\?\), which are commonly produced by std::fs::canonicalize() on Windows. See issue #30 for details.
This fix is now available in the upstream crate.
Specified in the rust-version field in Cargo.toml.
All the code in this repository is released under the MIT License, for more information, please read COPYRIGHT file.