/**
 * The path a filesystem's ref ids use (design §13): '/' separators, no '.' or '..' segments, no leading or
 * trailing '/', '' for the root. An absolute path inside `basePath` becomes relative to it; any other rooted
 * path without a drive (`/x`, `\x`) is relative to the filesystem root, as fsNative.resolvePath reads it. A
 * driveless rooted path is never inside a drive or UNC base path: on Windows `\data\up\x` with the base
 * `C:\data\up` gives `data/up/x`, while fsNative would read the base itself on the current drive.
 *
 * The guard hands this normalised path, not the caller's, to the raw provider, so the path it checks is the
 * path the provider touches, also on providers that use keys verbatim (S3: `/x` and `x` would be two keys).
 *
 * @throws InvalidArgument for a path that climbs above the root, holds a NUL byte, is a drive or UNC path
 * outside `basePath`, or has a segment holding ':' or ending in '.' or a space
 */
export declare function normalizeFsPath(path: string, basePath?: string): string;
//# sourceMappingURL=paths.d.ts.map