export interface ProjectPath { /** Absolute directory the project is written to. */ dir: string; /** * The project's name: the last segment of the path, and nothing else. * * `package.json`'s `name` cannot hold a path, so `/tmp/demo/my-app` names a * project `my-app`. For the ordinary `create-litro my-app` this is the * argument unchanged, which is what it has always been. */ name: string; /** * The path to print back to the user, as they typed it — so `cd ` * is a command they can run. A leading `~` is shown expanded, because a * silent expansion is the thing worth showing. */ display: string; } /** * Resolve the project argument into a directory, a name and something to print. * * @param input The path as typed: relative, absolute, or `~`-prefixed. * @param cwd The directory a relative path is resolved against. * * @throws When the path cannot be used — a `~user` form this cannot expand, or * a path with no last segment to name the project after. */ export declare function resolveProjectPath(input: string, cwd?: string): ProjectPath; /** Resolve a directory argument such as `--for-repo`, honoring a leading `~`. */ export declare function resolveUserPath(input: string, cwd?: string): string; /** * The path from a repository root down to the docs site inside it. * * `--for-repo` writes this into published files: the starlight config's * `editUrlBase`, which becomes an "Edit this page" link on GitHub, and the * heading of the generated `AGENTS.md`. A site outside the repository produces * a path with `..` in it, and `.../edit/main/../out/site/content/docs` is a * link that does not resolve. Refuse instead of publishing a broken link. * * @param repoDir Absolute path to the repository root. * @param siteDir Absolute path the site is scaffolded into. * * @throws When the site is not inside the repository. */ export declare function siteRelativeToRepo(repoDir: string, siteDir: string): string; //# sourceMappingURL=project-path.d.ts.map