import { GeneratedFile, GeneratedFolder, ComponentUIDL, ProjectUIDL, ProjectStrategy, UIDLPageOptions, ComponentGenerator, ComponentPlugin, PostProcessor, Mapping, StyleVariation, GeneratorFactoryParams, UIDLRouteDefinitions } from '@teleporthq/teleport-types'; export declare const createPageUIDLs: (uidl: ProjectUIDL, strategy: ProjectStrategy) => ComponentUIDL[]; /** * A couple of different cases which need to be handled * In case of next/nuxt generators, the file names represent the urls of the pages * Also the root path needs to be represented by the index file */ export declare const extractPageOptions: (routeDefinitions: UIDLRouteDefinitions, routeName: string, useFileNameForNavigation?: boolean) => { pageOptions: UIDLPageOptions; isHomePage: boolean; }; export declare const prepareComponentOutputOptions: (components: Record, strategy: ProjectStrategy) => void; export declare const resolveLocalDependencies: (pageUIDLs: ComponentUIDL[], components: Record, strategy: ProjectStrategy) => void; export declare const fileFileAndReplaceContent: (files: GeneratedFile[], fileName: string, content: string) => GeneratedFile[]; export declare const generateExternalCSSImports: (uidl: ComponentUIDL) => Promise; export declare const injectFilesToPath: (rootFolder: GeneratedFolder, path: string[], files: GeneratedFile[]) => void; export declare const bootstrapGenerator: ({ generator, plugins, postprocessors, mappings, }: { generator: (params: GeneratorFactoryParams) => ComponentGenerator; plugins?: ComponentPlugin[]; postprocessors?: PostProcessor[]; mappings?: Mapping[]; }, style?: StyleVariation, strictHtmlWhitespaceSensitivity?: boolean) => ComponentGenerator; /** * Last line of defence against "Module not found" builds: walk the finished * project and report every relative import that resolves to no generated file. * * A plugin that computes an import path from the wrong base (a page folder path * measured from `pages/` against a folder measured from the project root, say) * produces a project that looks complete and only breaks when the framework * compiles it — on the user's machine, or on Vercel. This puts the failure back * next to the code that caused it. * * Reports, never throws: the scan is text-based, so a string literal that merely * LOOKS like an import could show up here, and no generation should ever be * lost to that. `teleport-test`'s standalone run turns the same check into a * non-zero exit code, which is where a regression gets caught for real. */ export declare const reportUnresolvedLocalImports: (rootFolder: GeneratedFolder) => void; //# sourceMappingURL=utils.d.ts.map