/** A manifest, as far as anything here reads it. */ export interface Manifest { name?: string; version?: string; main?: string; module?: string; types?: string; bin?: string | Record; exports?: Exports; scripts?: Record; files?: string[]; dependencies?: Record; peerDependencies?: Record; [field: string]: unknown; } /** What a manifest's `exports` can hold, down to the paths a release rewrites. */ export type Exports = string | { [key: string]: Exports; }; /** * The manifest a package publishes, made from the one it is developed under. * * The two differ because they describe different trees. In the repository a * package is its source, so its entry points name `.ts` files and its siblings * are `workspace:` ranges. What goes out is the build, published from `dist` * with that directory as its root, so the same entry points name the `.js` and * `.d.ts` beside them and the siblings name the version going out with them. * * Generating it is what keeps the source out of the tarball: nothing has to be * described twice, and the manifest a developer reads never has to pretend it * is describing a package that has been built. */ export declare function published(manifest: Manifest): Manifest;