/**
 * VFS path utilities for compiled Deno binaries.
 *
 * In compiled binaries, import.meta.url resolves to embedded paths like
 * /tmp/deno-compile-xyz/Users/original/path/src/... which preserve the original
 * absolute path structure after the extraction root. These utilities handle
 * path resolution across both dev and compiled contexts.
 *
 * Key insight: Deno compile with --include embeds files with their original
 * absolute paths, and those files are accessible via those original paths
 * at runtime (Deno's VFS maps them transparently).
 */
/**
 * Get the framework root directory from a file path.
 * Handles both dev paths and compiled binary VFS paths.
 *
 * For compiled binaries, files are embedded with --include and extracted to:
 *   /tmp/deno-compile-xxx/{relative_path_from_include}
 *
 * The extraction root IS the framework root because --include paths are
 * relative to the project root. So dist/framework-src extracts to
 * /tmp/deno-compile-xxx/dist/framework-src.
 */
export declare function getFrameworkRoot(filePath: string): string;
/**
 * Get the framework root from import.meta.url.
 * Convenience wrapper for module-level initialization.
 */
export declare function getFrameworkRootFromMeta(importMetaUrl: string): string;
/** Testable version for unit tests. */
export declare function testGetFrameworkRoot(filePath: string): string;
//# sourceMappingURL=vfs-paths.d.ts.map