@arcgis/lumina-compiler 5.2.0-next.2 → 5.2.0-next.21

package/dist/useLumina.d.ts

@@ -1,4 +1,5 @@
-import { LuminaPlugins, LuminaOptions } from './publicTypes.ts';
+import type { LuminaPlugins, LuminaOptions } from "./options.js";
+
 /**
  * Auto-configure Vite for a Lit web component project.
  *
@@ -9,5 +10,7 @@ import { LuminaPlugins, LuminaOptions } from './publicTypes.ts';
  * - Separate bundle for each component to bundle only the necessary code
  * - Generates types, docs, and api.json for web components
  * - Generates a CDN build
+ *
+ * @param options
  */
-export declare function useLumina(options?: LuminaOptions): LuminaPlugins;
+export function useLumina(options?: LuminaOptions): LuminaPlugins;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arcgis/lumina-compiler",
-  "version": "5.2.0-next.2",
+  "version": "5.2.0-next.21",
   "description": "Compiler for WebGIS web components",
   "type": "module",
   "main": "./dist/index.js",
@@ -12,6 +12,12 @@
     "./puppeteerTesting": "./dist/puppeteerTesting/index.js",
     "./puppeteerTesting/globalSetup": "./dist/puppeteerTesting/globalSetup.js",
     "./puppeteerTesting/runner": "./dist/puppeteerTesting/vitest/runner.js",
+    "./docs/vsCodeCustomData/types": {
+      "types": "./dist/docs/vsCodeCustomData/types.d.ts"
+    },
+    "./docs/webTypes/types": {
+      "types": "./dist/docs/webTypes/types.d.ts"
+    },
     "./package.json": "./package.json"
   },
   "files": [
@@ -19,25 +25,27 @@
   ],
   "license": "SEE LICENSE IN LICENSE.md",
   "dependencies": {
-    "@vitest/expect": "^4.1.6",
-    "@vitest/runner": "^4.1.6",
     "esbuild": "~0.28.0",
     "js-beautify": "^1.15.4",
     "mime-types": "^3.0.1",
     "tinyglobby": "^0.2.15",
     "tslib": "^2.8.1",
-    "@arcgis/api-extractor": "5.2.0-next.2",
-    "@arcgis/components-build-utils": "5.2.0-next.2",
-    "@arcgis/toolkit": "~5.2.0-next.2"
+    "@arcgis/api-extractor": "5.2.0-next.21",
+    "@arcgis/components-build-utils": "5.2.0-next.21",
+    "@arcgis/toolkit": "~5.2.0-next.21"
   },
   "peerDependencies": {
     "lit": "^3.3.0",
+    "puppeteer": "^24.30.0",
     "typescript": "~6.0.2",
     "vite": "^7.3.2",
     "vitest": "^4.1.6",
-    "@arcgis/lumina": "~5.2.0-next.2"
+    "@arcgis/lumina": "~5.2.0-next.21"
   },
   "peerDependenciesMeta": {
+    "puppeteer": {
+      "optional": true
+    },
     "vitest": {
       "optional": true
     }

package/dist/context/logger.d.ts

@@ -1,8 +0,0 @@
-import { createLogger } from 'vite';
-export declare const logger: {
-    initialize(logger: ReturnType<typeof createLogger>, root: string): void;
-    info(scope: string, message: string, file?: string): void;
-    warn(scope: string, message: string, file?: string): void;
-    error(scope: string, message: string, file?: string): void;
-};
-export declare function formatError<T extends Error | string>(scope: string, messageOrError: T, file?: string): T;

package/dist/context/typeScript.d.ts

@@ -1,6 +0,0 @@
-import { CompilerContext } from './index.ts';
-/**
- * Convert TypeScript ECMA target version number into an ESBuild target version
- * string
- */
-export declare function resolveTargetVersion(context: CompilerContext): string;

package/dist/context/utils.d.ts

@@ -1,4 +0,0 @@
-export declare function inferPreamble(packageJson?: import('@arcgis/components-build-utils').PackageJson): string;
-export declare const preambleToComment: (preamble: string) => string;
-export declare const throwOnReadBeforeSet: (createdDuring: string) => PropertyDecorator;
-export declare function normalizeDocumentationFileName(fileName: string): string;

package/dist/dependencies/arcgisCore.d.ts

@@ -1,30 +0,0 @@
-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[]>;

package/dist/dependencies/index.d.ts

@@ -1,12 +0,0 @@
-import { IndexHtmlTransformContext, Plugin } from 'vite';
-import { CompilerContext } from '../context/index.ts';
-export declare const doLoadersApply: (context: CompilerContext, htmlContext?: IndexHtmlTransformContext) => boolean;
-/**
- * In serve mode, augment index.html by adding the necessary script tags for
- * each web component dependency.
- *
- * In case of Storybook, we apply this plugin to iframe.html, not just in serve
- * mode, but also in build mode.
- *
- */
-export declare const provideDependencySupport: (context: CompilerContext) => Plugin;

package/dist/dependencies/loaders.d.ts

@@ -1,5 +0,0 @@
-import { CompilerContext } from '../context/index.ts';
-import { ResolvedDependencyComponents } from './discover.ts';
-import { DependencyInjectionResult } from './utils.ts';
-export declare function makeLoaders(context: CompilerContext): Promise<DependencyInjectionResult[]>;
-export declare function computeServeOnlyDependencies(context: CompilerContext): Promise<readonly ResolvedDependencyComponents[]>;

package/dist/dependencies/lumina.d.ts

@@ -1,3 +0,0 @@
-import { DependencyInjectionMode, DependencyInjectionResult } from './utils.ts';
-import { ResolvedDependencyComponents } from './discover.ts';
-export declare function makeLuminaLoader(baseUrl: string, dependency: ResolvedDependencyComponents, mode: DependencyInjectionMode, index: number, preferNext: boolean): Promise<DependencyInjectionResult>;

package/dist/dependencies/stencil.d.ts

@@ -1,17 +0,0 @@
-import { DependencyInjectionMode, DependencyInjectionResult } from './utils.ts';
-import { ResolvedDependencyComponents } from './discover.ts';
-export declare function makeStencilLoader(baseUrl: string, dependency: ResolvedDependencyComponents, mode: DependencyInjectionMode, index: number, preferNext: boolean): Promise<DependencyInjectionResult[]>;
-export declare function findCdnFiles(packageDirectory: string): Promise<{
-    readonly cdnName: string;
-    readonly hasCss: boolean;
-} | undefined>;
-export type StencilLazyLoadingData = LazyBundleRuntimeData[];
-type LazyBundleRuntimeData = [string, ComponentRuntimeMetaCompact[]];
-type ComponentRuntimeMetaCompact = [
-    number,
-    /** tagname */
-    string,
-    /** members */
-    Record<string, [number, string?]>?
-];
-export {};

package/dist/dependencies/testSetupFiles.d.ts

@@ -1,13 +0,0 @@
-import { CompilerContext } from '../context/index.ts';
-export declare const testSetupFileRegex: RegExp;
-export declare const testSetupFileNames: string[];
-/**
- * Get the entrypoint code for lazy-loading all components and their
- * dependencies when running a web component test in the browser.
- *
- * Lazy loading is critical for performance. Since each test runs in isolation,
- * we wouldn't want to load all possible components in each test (and tracking
- * precisely which components were used is tricky and bug prone - i.e won't
- * catch dynamic references).
- */
-export declare function buildTestSetupFile(context: CompilerContext): Promise<string>;

package/dist/dependencies/utils.d.ts

@@ -1,15 +0,0 @@
-import { HtmlTagDescriptor } from 'vite';
-export type DependencyInjectionMode = "cdn" | "lazyNpm";
-export type DependencyInjectionResult = HtmlTagDescriptor | {
-    cssHref: string;
-    id?: string;
-} | {
-    optimizableImports: string[];
-    javascriptCode: string[];
-};
-/**
- * The `baseUrl` should be set to `context.viteConfig.base`
- * Vite always normalized `base` to end with `/`, and, if in serve mode, to not
- * include domain name
- */
-export declare const toFsUrl: (baseUrl: string, absolutePath: string) => string;

package/dist/docs/config.d.ts

@@ -1,9 +0,0 @@
-import { CompilerContext } from '../context/index.ts';
-import { DocsType } from './types.ts';
-export declare const defaultDocsFileNames: Record<DocsType, string>;
-/**
- * Minify docs .json files to reduce node_modules size (otherwise they account
- * for 50% of component package size). Don't minify if Lumina is running in AWC's
- * test package to allow for build snapshot diffs
- */
-export declare const getDocsFileIndent: (context: CompilerContext) => 2 | undefined;

package/dist/docs/index.d.ts

@@ -1,10 +0,0 @@
-import { CompilerContext } from '../context/index.ts';
-import { Plugin } from 'vite';
-/**
- * Generate JSON component metadata in 4 formats
- * - community standard
- * - Stencil-like format
- * - VS Code standard
- * - JetBrains standard
- */
-export declare function generateDocs(context: CompilerContext): Plugin;

package/dist/docs/stencilDocsJson.d.ts

@@ -1,130 +0,0 @@
-import { CompilerContext } from '../context/index.ts';
-import { ApiDocsTag } from '@arcgis/api-extractor/apiJson';
-/**
- * To avoid having a dependency on Stencil, we inline Stencil types rather than
- * importing them.
- */
-interface JsonDocs {
-    deprecation?: string;
-    components: JsonDocsComponent[];
-    timestamp: string;
-    compiler: {
-        name: string;
-        version: string;
-        typescriptVersion: string;
-    };
-    typeLibrary: Record<string, never>;
-}
-interface JsonDocsComponent {
-    filePath?: string;
-    encapsulation: "none" | "scoped" | "shadow";
-    tag: string;
-    readme: string;
-    docs: string;
-    docsTags: ApiDocsTag[];
-    overview?: string;
-    usage: Record<string, string>;
-    props: JsonDocsProp[];
-    methods: JsonDocsMethod[];
-    events: JsonDocsEvent[];
-    listeners: never[];
-    styles: {
-        name: string;
-        docs: string;
-        annotation: string;
-        mode: string | undefined;
-    }[];
-    slots: {
-        name: string;
-        docs: string;
-    }[];
-    parts: {
-        name: string;
-        docs: string;
-    }[];
-    dependents: string[];
-    dependencies: string[];
-    dependencyGraph: Record<string, never>;
-    deprecation?: string;
-}
-interface JsonDocsEvent {
-    event: string;
-    bubbles: boolean;
-    cancelable: boolean;
-    composed: boolean;
-    complexType: ComplexType;
-    docs: string;
-    docsTags: ApiDocsTag[];
-    deprecation?: string;
-    detail: string;
-}
-interface ComponentCompilerMethodComplexType {
-    signature: string;
-    parameters: {
-        name: string;
-        type: string;
-        docs: string;
-    }[];
-    references: ComponentCompilerTypeReferences;
-    return: string;
-}
-type ComponentCompilerTypeReferences = Record<string, {
-    location: "global" | "import" | "local";
-    path?: string;
-    id: string;
-}>;
-interface JsonDocsMethod {
-    name: string;
-    docs: string;
-    docsTags: ApiDocsTag[];
-    deprecation?: string;
-    signature: string;
-    returns: {
-        type: string;
-        docs: string;
-    };
-    parameters: ComponentCompilerMethodComplexType["parameters"];
-    complexType: ComponentCompilerMethodComplexType;
-}
-interface ComplexType {
-    original: string;
-    resolved: string;
-    references: ComponentCompilerTypeReferences;
-}
-interface JsonDocsProp {
-    name: string;
-    complexType?: ComplexType;
-    type: string;
-    mutable: boolean;
-    attr?: string;
-    reflectToAttr: boolean;
-    docs: string;
-    docsTags: ApiDocsTag[];
-    default?: string;
-    deprecation?: string;
-    values: {
-        value?: string;
-        type: string;
-    }[];
-    optional: boolean;
-    required: boolean;
-}
-/**
- * Create a stencil-compatible docs.json file describing the library components.
- *
- * While custom-elements-manifest is the most popular community standard and is
- * natively supported by Storybook and other tools, Esri has several internal
- * tools that expect the Stencil-style docs.json.
- * Since they are similar in content, generating a Stencil-compatible docs.json
- * will smooth the migration path.
- *
- * REFACTOR: drop support for stencil compatible docs.json at some point
- *
- * @remarks
- * To make it easier for people to diff the docs.json before and after migration
- * to Lit, we make sure that the order of properties matches what Stencil
- * generates:
- * https://github.com/ionic-team/stencil/blob/9f5f9cdd023b8c8dfb5417a1a970605ba724ae28/src/compiler/docs/generate-doc-data.ts#L98
- */
-export declare const generateStencilDocsJson: (context: CompilerContext) => JsonDocs;
-export {};

package/dist/docs/types.d.ts

@@ -1 +0,0 @@
-export type DocsType = "apiJson" | "stencilLikeDocsJson" | "vsCodeCss" | "vsCodeHtml" | "webTypes";

package/dist/docs/vsCodeCustomData/index.d.ts

@@ -1,16 +0,0 @@
-import { VsCodeHtmlDocs, VsCodeCssDocs } from './types.ts';
-import { ApiCustomElementDeclaration } from '@arcgis/api-extractor/apiJson';
-/**
- * Originally based on
- * https://github.com/break-stuff/cem-tools/tree/main/packages/vs-code-integration
- *
- * Moved in house mainly because of
- * https://github.com/prettier/prettier-synchronized/issues/22
- * That issue affects all debuggers, not just VS Code, and since the cause is
- * in the global scope, it affects the program even if generateWebTypes wasn't
- * called.
- *
- * But also there are several other quality issues with the original plugin.
- */
-export declare const generateVsCodeHtmlCustomData: (components: ApiCustomElementDeclaration[]) => VsCodeHtmlDocs;
-export declare const generateVsCodeCssCustomData: (components: ApiCustomElementDeclaration[]) => VsCodeCssDocs;

package/dist/docs/vsCodeCustomData/utils.d.ts

@@ -1,3 +0,0 @@
-import { VsCodeTag } from './types.ts';
-import { ApiCustomElementDeclaration } from '@arcgis/api-extractor/apiJson';
-export declare const getTagList: (components: ApiCustomElementDeclaration[]) => VsCodeTag[];

package/dist/docs/webTypes/description.d.ts

@@ -1,2 +0,0 @@
-import { ApiCustomElementDeclaration } from '@arcgis/api-extractor/apiJson';
-export declare function getComponentDetailsTemplate(component: ApiCustomElementDeclaration): string;

package/dist/docs/webTypes/index.d.ts

@@ -1,19 +0,0 @@
-import { WebTypesOptions, WebTypes } from './types.ts';
-import { ApiCustomElementDeclaration } from '@arcgis/api-extractor/apiJson';
-/**
- * Originally based on
- * https://github.com/break-stuff/cem-tools/tree/main/packages/jet-brains-integration
- *
- * Moved in house mainly because of
- * https://github.com/prettier/prettier-synchronized/issues/22
- * That issue affects all debuggers, not just VS Code, and since the cause is
- * in the global scope, it affects the program even if generateWebTypes wasn't
- * called.
- *
- * But also there are several other quality issues with the original plugin,
- * including:
- * - https://github.com/break-stuff/cem-tools/issues/151
- * - https://github.com/break-stuff/cem-tools/issues/141
- * - https://github.com/break-stuff/cem-tools/issues/112
- */
-export declare function generateWebTypes(components: ApiCustomElementDeclaration[], options: WebTypesOptions): WebTypes;

package/dist/docs/webTypes/utils.d.ts

@@ -1,6 +0,0 @@
-import { ApiCustomElementDeclaration } from '@arcgis/api-extractor/apiJson';
-import { WebTypesAttribute, WebTypesCssProperty, WebTypesPseudoElement } from './types.ts';
-export declare const getCssPropertyList: (components: ApiCustomElementDeclaration[]) => WebTypesCssProperty[];
-export declare const getCssPartList: (components: ApiCustomElementDeclaration[]) => WebTypesPseudoElement[];
-export declare function getComponentAttributes(component: ApiCustomElementDeclaration): WebTypesAttribute[];
-export declare const formatDescription: (description?: string, deprecated?: boolean | string) => string;

package/dist/entrypoints/addNonLazyImports.d.ts

@@ -1,13 +0,0 @@
-import { Plugin } from 'vite';
-import { CompilerContext } from '../context/index.ts';
-/**
- * When component is imported in a non-lazy-loading way, we need to make sure
- * the component file has explicit import statements for all web component it
- * depends on - this ensures dependencies get bundled correctly.
- *
- * However, in lazy-loading mode, we don't need to do this because all dependent
- * components are assumed to be lazy-loadable too.
- *
- * This plugin creates an index.js for each component for non-lazy-loading mode.
- */
-export declare const addNonLazyImports: (context: CompilerContext) => Plugin;

package/dist/entrypoints/config.d.ts

@@ -1,17 +0,0 @@
-export declare const customElementEntrypointName = "customElement.js";
-export type CustomElementInterdependencies = Record<string, {
-    /**
-     * All local or foreign custom elements referenced in current file.
-     *
-     * If this is a component entrypoint file, these imports will be added to
-     * the component-name/index.js file so that non-lazy esm usages would
-     * include this import.
-     * If this is not an entrypoint file (i.e a util functional component), then
-     * the referencedBy array will be used to find the entrypoint files that
-     * referenced this file (directly or indirectly), and any import specifiers
-     * will be added to those components instead of this file.
-     */
-    referencedTagNames: string[];
-    referencedDeferredTagNames: string[];
-    readonly referencedBy: string[];
-}>;

package/dist/entrypoints/dtsUtils.d.ts

@@ -1,19 +0,0 @@
-import { path } from '@arcgis/components-build-utils';
-import { CompilerContext } from '../context/index.ts';
-/**
- * Rewrite references to `./components/component-folder-name/component-file-name.js` with
- * `./components/component-tag-name/customElement.js` in `.js` and `.d.ts` files.
- *
- * @remarks
- * Assuming content includes POSIX paths only (as that's what import specifiers
- * in ECMAScript use)
- */
-export declare const rewriteComponentImportSpecifiers: (code: string, context: Pick<CompilerContext, "apiExtractor" | "dir">, cwd: string, originalCwd: string) => string;
-/**
- * The result of relative() is a path that does not start with `./`.
- * In import statements the path must begin with ../ or ./ to be interpreted as
- * a relative path rather than a package name.
- * This function makes sure that the result of relative() is normalized to start
- * with `./` or `../`
- */
-export declare const toRelativeImportSpecifier: (typeof path)["relative"];

package/dist/entrypoints/findUtils.d.ts

@@ -1,6 +0,0 @@
-/**
- * @example
- * `src/components/component-name/component-name.tsx` =>
- * `./components/component-name/customElement`
- */
-export declare const entrypointPathToDistPath: (sourceFileName: string, srcPath?: string) => string;

package/dist/entrypoints/handleComponentImports.d.ts

@@ -1,13 +0,0 @@
-import { default as ts } from 'typescript';
-import { JsxContext } from '../jsxToLitHtml/types.ts';
-/**
- * Instead of adding imports to the component source file, take note of imports
- * that need to be added and have addNonLazyImports() add them to component's
- * component-name/index.js (rather than component-name/customElement.js)
- *
- * Since component-name/index.js file is only imported in non-lazy builds, it
- * will make sure to bundle-in used components. In lazy builds, it is expected
- * that "defineCustomElements()" of some sort is called separately to load the
- * components this file depends on.
- */
-export declare function handleComponentImports(context: JsxContext): ts.ImportDeclaration[];

package/dist/entrypoints/resolveTagName.d.ts

@@ -1,18 +0,0 @@
-import { ResolvedDependencyComponent } from '../dependencies/discover.ts';
-import { CompilerContext } from '../context/index.ts';
-/**
- * Automatically add imports as appropriate for all referenced internally defined
- * and externally defined custom elements
- */
-export declare function resolveTagName(context: CompilerContext, tagName: string, fileName: string): {
-    packageName: string | undefined;
-    modulePath: string;
-} | undefined;
-export declare function modulePathToString(resolvedPath: {
-    packageName: string | undefined;
-    modulePath: string;
-}, distRelativeCwd: string): string;
-export declare function getLocalDefinedComponentsFromApiJson(context: Pick<CompilerContext, "_localDefinedComponents" | "privateApiJson" | "viteCommand">): Readonly<Record<string, ResolvedDependencyComponent>>;
-export declare const exportsForTests: {
-    modulePathToString: typeof modulePathToString;
-};

package/dist/jsxToLitHtml/autoAddNothing.d.ts

@@ -1,8 +0,0 @@
-import { TemplatePart } from './templateParts.ts';
-import { JsxContext } from './types.ts';
-/**
- * If JSX prop value could possibly be `undefined`, we add `?? nothing` to it.
- *
- * See comment on ElementPropertyToAttributeMappings.stringified for reason why.
- */
-export declare function autoAddNullishFallback(part: TemplatePart, context: JsxContext, defaultValue?: string): TemplatePart;

package/dist/jsxToLitHtml/comments.d.ts

@@ -1,19 +0,0 @@
-import { default as ts } from 'typescript';
-import { JsxContext } from './types.ts';
-import { TemplatePart } from './templateParts.ts';
-/**
- * Extract comments and whitespace from a node (called "trivia" in TypeScript)
- */
-export declare const getNodeTrivia: (node: ts.Node, context: Pick<JsxContext, "sourceFile">) => string;
-/**
- * Attach trivia comments to a node.
- *
- * @remarks
- * Does not attach whitespace as doing so in TypeScript AST is much harder than
- * it seems. There is one hacky workaround, but I could easily see it break
- * something: https://stackoverflow.com/a/69240365/8584605
- */
-export declare function attachComments<T extends ts.Node>(triviaText: string, node: T): T;
-export declare const findCommentRanges: (trivia: string) => ts.CommentRange[];
-/** Convert trivia into parts that can be converted to template expressions */
-export declare function triviaToTemplateParts(trivia: string): TemplatePart[];

package/dist/jsxToLitHtml/convertProps.d.ts

@@ -1,10 +0,0 @@
-import { default as ts } from 'typescript';
-import { TemplatePart } from './templateParts.ts';
-import { JsxContext } from './types.ts';
-import { JsxPropType } from './inferPropType.ts';
-import { dynamicHtmlSymbol, dynamicSvgSymbol } from './config.ts';
-/**
- * Handle the conversion for each JSX prop type
- */
-export declare const convertProps: Record<JsxPropType, (context: JsxContext, initializer: ts.JsxAttributeValue | undefined, propName: string, tagName: string | typeof dynamicHtmlSymbol | typeof dynamicSvgSymbol) => TemplatePart[]>;
-export declare function keyInitializerToExpression(initializer: ts.JsxAttributeValue | undefined, sourceFile: ts.SourceFile): ts.Expression;

package/dist/jsxToLitHtml/imports.d.ts

@@ -1,27 +0,0 @@
-import { default as ts } from 'typescript';
-import { JsxContext } from './types.ts';
-/**
- * This runs before we know what imports will be needed.
- *
- * 1. Go though all import paths and take note of them to inform us later if
- *    some custom element import still need or need not be added
- * 2. Take note of all the existing Lit imports. Otherwise, when inserting
- *    imports, if we see that e.x "html" is not present in the "lit" import, we
- *    might import it again and fail to check that it might be imported further
- *    down from "lit-html".
- * 3. Drop compiler-only imports that exist as runtime imports only for
- *    type checking or as compiler hints.
- */
-export declare function trackExistingImports(context: JsxContext, importDeclaration: ts.ImportDeclaration): ts.ImportDeclaration | undefined;
-/**
- * After we know what imports will be needed, if there already are some imports
- * from the places we are looking for, augment those import declarations.
- *
- * In a step after this, if any imports will still be needed, we will add them.
- */
-export declare function augmentExistingImports(this: JsxContext, node: ts.Statement): ts.Statement;
-/**
- * For each remaining needed import that is not already included, add an
- * import declaration
- */
-export declare function addMissingLitImports(context: JsxContext): ts.ImportDeclaration[];

package/dist/jsxToLitHtml/importsConfig.d.ts

@@ -1,17 +0,0 @@
-import { JsxImportName } from './types.ts';
-/**
- * Most Lit API's are re-exported from multiple packages. Because only Lit
- * package is declared as an explicit dependency, Lumina's auto-inserted imports
- * should only import from the Lit package (from the first import path in the
- * lists below). However, to avoid double-importing things if the file already
- * imports these APIs from another package, we need to check for all the places
- * that export these APIs (the 2nd+ items in the lists below).
- */
-export declare const dynamicallyInsertedImportsByName: Record<JsxImportName, string[]>;
-/**
- * These runtime imports exist only for type checking or as compiler hints.
- * The compiler refactors out their usages. Thus, we should also remove out
- * their imports. This does not happen automatically if using TypeScript's
- * strict verbatimModuleSyntax setting.
- */
-export declare const compilerOnlyLuminaImports: Set<string>;

package/dist/jsxToLitHtml/index.d.ts

@@ -1,20 +0,0 @@
-import { FileTransformer } from '../publicTypes.ts';
-/**
- * Let developers author components in JSX for better type checking and developer
- * experience, but convert JSX to lit-html at build time for better performance.
- *
- * This TypeScript transformer converts JSX expressions to lit-html tagged
- * literals, adding necessary imports in the process
- *
- * @remarks
- * If you wish to explicitly opt-out of JSX to lit-html transform in a given
- * file, you can do so by specifying a `@jsx` pragma at the top of the file.
- * For example, to use React JSX in a file, add the following at the top:
- * ```ts
- * /** @jsx React.createElement *\/
- * ```
- *
- * Also, if you import JSX from non-Lumina library, the transform will also be
- * disabled for that file.
- */
-export declare const transformJsxToLitHtml: FileTransformer;