import { ComponentPlugin, ComponentPluginFactory } from '@teleporthq/teleport-types';
/**
 * Tail-of-pipeline finalizer for entity-bound pages that
 * `createStaticPropsPlugin` (teleport-plugin-next-static-props) tagged with
 * `meta.useServerSideProps` on the 'getStaticProps' chunk — i.e. dynamic
 * pages that read one specific row AND have a same-page workflow that
 * writes to that same table (see `pageHasSameTableMutationWorkflow`'s doc in
 * that package for why this is a data-correctness signal, independent of
 * the project's visual nav layout) — and for every page that reads a money
 * table (`pageReadsProtectedTable`), whose getStaticProps chunk is usually
 * created by the data-source or pagination plugin, which never tag it.
 *
 * Every OTHER page plugin that fetches data (inline-fetch, data-source,
 * pagination, state-data-source, locale-fetcher) finds / merges additional
 * fetches into that chunk by its literal name `'getStaticProps'` — so the
 * chunk MUST keep that name for the entire per-page plugin pipeline, or
 * every one of those lookups would miss and each would spawn its OWN
 * second, conflicting `getStaticProps` function on the same page. This
 * plugin is registered LAST (after every data-fetching plugin) and performs
 * the actual getStaticProps -> getServerSideProps conversion once nothing
 * downstream needs to find the chunk by its original name:
 *   1. Renames the function identifier + the chunk itself.
 *   2. Strips any `revalidate` property later plugins attached (invalid on
 *      getServerSideProps — Next.js throws a build-time error if present).
 */
export declare const createEntityMutationSsrFinalizerPlugin: ComponentPluginFactory<Record<string, never>>;
declare const _default: ComponentPlugin;
export default _default;
//# sourceMappingURL=entity-mutation-ssr-finalize-plugin.d.ts.map