/**
 * What `"workspace:*"` becomes — the one line to change when this is wrong.
 *
 * The scaffolder and the framework ship from the same repository at the same version,
 * so `create-assemora@0.4.2` writes a project against `^0.4.2`: what it knows how to
 * scaffold is what it was built beside, and a caret keeps the project on that minor
 * line, which is the right width before 1.0.
 *
 * Today that version is `0.0.0` and nothing is published to npm, so a generated
 * project cannot be installed at all yet. The executable says so in as many words
 * rather than leaving somebody to read it out of a resolver error.
 */
export declare const dependencyRange: (version: string) => string;
/**
 * This package's own version.
 *
 * Read rather than compiled in, so a published build writes the version it was
 * published as. `package.json` sits one directory above both `src/` and `dist/`, so
 * the same URL is right under a test runner and after a build.
 */
export declare const packageVersion: () => Promise<string>;
/** Whether the framework this scaffolder belongs to has ever been released. */
export declare const isUnreleased: (version: string) => boolean;
export type PackageJsonOptions = {
    /** The project's name. Left alone for a `package.json` below the template root. */
    readonly name?: string;
    /** What every `workspace:` range becomes. */
    readonly range: string;
    /** Package names to remove, because the feature that wanted them was declined. */
    readonly drop: readonly string[];
    /** Script names to remove, for the same reason. A script is not a dependency. */
    readonly dropScripts?: readonly string[];
};
/**
 * A template's `package.json`, as the project's.
 *
 * Sections are rebuilt in their original key order rather than mutated, so the file
 * a developer opens has its dependencies where its author put them.
 */
export declare const projectPackageJson: (source: string, file: string, options: PackageJsonOptions) => string;
//# sourceMappingURL=package-json.d.ts.map