import { DependencyInjectionMode, DependencyInjectionResult } from './utils.ts';
export declare const hasCore: boolean;
/**
 * Thanks to Vite's dependency pre-bundling, we do not have to use the CDN
 * during local development, but can instead consume the pre-bundled
 * `@arcgis/core` from the node_modules directory.
 *
 * This has benefits:
 * - using the ESM CDN involves making a lot of network requests, often for
 *   small files. With pre-bundling, performance can be improved
 * - by using `@arcgis/core` from node_modules, the dev server is guaranteed to
 *   use the version of `@arcgis/core` that the package.json specifies. Where as
 *   the CDN could be out of date, or point to `next` (which is somewhat
 *   ambiguous around release time)
 * - by using `@arcgis/core` from node_modules, you can edit the package in
 *   node_modules to quickly preview the result of your edits. This is useful
 *   if you are debugging a bug and not yet sure if the bug is with your package
 *   or with `@arcgis/core`. More on this:
 *   https://vitejs.dev/guide/dep-pre-bundling#browser-cache
 *
 * In builds, all dependencies are externalized so this is not a concern.
 *
 * In storybook builds, we use the ESM CDN. Reasons:
 * - dependency pre-bundling is not available in build mode, only in serve mode
 * - bundling `@arcgis/core` makes the build output huge, creating logistical
 *   challenges around deploying many preview branches
 * - for external users, having both storybook and docs use the ESM CDN means
 *   they benefit from caching the ESM CDN across both sites
 */
export declare function produceArcgisCoreTags(baseUrl: string, mode: DependencyInjectionMode, preferNext: boolean): Promise<DependencyInjectionResult[]>;