import type { Plugin } from "unified";
import type { Program } from "estree";
type TargetTag = "a" | "img" | "video" | "audio" | "source" | "code";
declare const MapOfTargetTagAttributes: Record<TargetTag, string | string[] | true>;
export type InterpolateOptions = {
    /**
     * Disable the plugin (for example when the format is not "mdx")
     */
    disable?: boolean;
    /**
     * Exclude specific tag and attributes
     */
    exclude?: Partial<typeof MapOfTargetTagAttributes>;
    /**
     * The syntax for interpolation in code fences,
     * default is "{{"; the reversed "}}" is implicitly used to close the interpolation.
     * For example, if you set it to "{{", then opening and closing syntax are both "{{" and "}}", then you can write:
     * \`\`\`bash
     * pnpm add @mdx-js/loader@{{props.versions.mdxJsLoader}}
     * \`\`\`
     * You can also set it to other values, such as "[[".
     * \`\`\`bash
     * pnpm add @mdx-js/loader@[[props.versions.mdxJsLoader]]
     * \`\`\`
     * The plugin
     * will look for the opening syntax (e.g., "{{" or "[[" or "<<:") and,
     * will use implicitly the closing syntax (e.g., "}}" or "]]" or ":>>") to identify the interpolation expressions in code fences.
     * This is useful when you want to avoid conflict with language specific syntaxes in code fences.
     * Note: this option only affects code fences, for other tags (a, img, video, audio, source), the syntax is always { and }.
     */
    interpolationSyntaxForCodeFence?: string;
    /**
     * Require interpolation expressions to have no leading or trailing spaces (only for code fences)
     * whitespace inside `{{` and `}}` (e.g. `{{name}}` instead of `{{ name }}`).
     */
    strict?: boolean;
};
/**
 * It is a recma plugin which transforms the esAST / esTree.
 *
 * It interpolates identifiers wrapped in curly braces in the alt/src/title of the links/images in MDX
 *
 */
declare const plugin: Plugin<[InterpolateOptions?], Program>;
export default plugin;
//# sourceMappingURL=index.d.ts.map