@arcgis/lumina-compiler 4.34.0-next.5 → 4.34.0-next.50

package/dist/jsxToLitHtml/importsConfig.d.ts

@@ -0,0 +1,10 @@
+import { JsxImportName } from './types';
+/**
+ * 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[]>;

package/dist/plugins/loadLitCss.d.ts

@@ -84,3 +84,4 @@ export declare const globalCssFlag = "?global";
  * will be inlined as base64 to simplify our life.
  */
 export declare const loadLitCss: (context: CompilerContext) => Plugin;
+export declare function viteCssModuleToLit(code: string, withHmr: boolean, minify: boolean, isLayered: boolean): string;

package/dist/publicTypes.d.ts

@@ -3,9 +3,9 @@ import { Plugin } from 'vite';
 import { build as esbuildBuild } from 'esbuild';
 import { CompilerContext } from './context';
 import { PluginOptions as VitePluginDtsOptions } from 'vite-plugin-dts';
-import { ExternalsOptions as RollupPluginNodeExternalsOptions } from 'rollup-plugin-node-externals';
 import { WebTypesOptions } from './docs/webTypes/types';
 import { VsCodeDocOptions } from './docs/vsCodeCustomData/types';
+import { DependencyManagementOptions as BaseDependencyManagementOptions } from '@arcgis/components-build-utils';
 import { ApiJson, ApiModule, CopyDocDefinitions } from '@arcgis/api-extractor';
 import { LuminaApiExtractor } from './extractor/extractor';
 /**
@@ -113,7 +113,6 @@ export type BuildOptions = {
      * Wrappers to generate.
      */
     readonly wrappers?: WrappersOptions[];
-    readonly ssr?: SsrOptions;
 };
 export type BuildCdnOptions = {
     /**
@@ -168,32 +167,6 @@ export type CdnChunk = {
  * https://devtopia.esri.com/WebGIS/arcgis-web-components/discussions/1281
  */
 export type WrappersOptions = React18WrapperOptions;
-export type SsrOptions = {
-    /**
-     * Emit output compatible with Stencil's dist-hydrate-script build.
-     *
-     * @deprecated
-     * This option should be used to smooth the migration path from Stencil.
-     * You should instruct your SSR users to migrate to Lit's SSR implementation,
-     * and then stop using this option.
-     *
-     * @see https://stenciljs.com/docs/hydrate-app
-     * @see https://lit.dev/docs/ssr/overview/
-     */
-    readonly stencilCompatibility?: {
-        /**
-         * @default false
-         */
-        enabled?: boolean;
-        /**
-         * By default, the hydrate directory is output to package root, outside
-         * of dist.
-         *
-         * @default "hydrate"
-         */
-        path?: string;
-    };
-};
 /**
  * Options for creating React 18 wrapper.
  *
@@ -211,46 +184,31 @@ export type React18WrapperOptions = {
 /**
  * Options for externalizing dependencies.
  *
- * Reuse the options from rollup-plugin-node-externals, but rename two options for clarity.
- * - `include` is renamed to `externalize` to make it clear that these are externalized
- * - `exclude` is renamed to `bundleIn` to make it clear that these are bundled in
- *
- * @see https://www.npmjs.com/package/rollup-plugin-node-externals
- *
  * @remarks
  * If Vite is running under Storybook, these options are ignored. This is
  * because in Storybook build, unlike in a library build, we want to bundle in
  * all dependencies (with exception of @arcgis/core and web component
  * dependencies, which are loaded using the ESM CDN).
  */
-export type DependencyManagementOptions = Omit<RollupPluginNodeExternalsOptions, "exclude" | "include"> & {
+export type DependencyManagementOptions = BaseDependencyManagementOptions & {
     /**
-     * Force bundle in these dependencies even if they are declared as
-     * dependencies or peerDependencies.
+     * By default, Lumina will error if it encounters usage of an unknown custom
+     * element. This setting allows to silence such error if you are manually
+     * importing some custom elements.
      *
-     * @example
-     * This is desirable if you wish to control the version of a dependency or
-     * need to post-process the dependency in some way. Usually, you will declare
-     * such as a devDependency, but there is a use case for declaring it as a
-     * dependency instead:
-     *
-     * - If TypeScript types from the bundled in dependencies are referenced in
-     *   the `.d.ts` files of your library, you will need to declare the package
-     *   as a `dependency`, so that it is still installed on the consumer's
-     *   computer so that TypeScript can correctly resolve the types of that
-     *   library.
-     */
-    readonly bundleIn?: NonNullable<RollupPluginNodeExternalsOptions>["exclude"];
-    /**
-     * Force externalize these dependencies, even if they are declared as
-     * devDependencies.
+     * > [!IMPORTANT]
+     * >
+     * > This option is an escape hatch. Build-time optimizations are not applied
+     * > to such custom elements. Additionally, you assume the responsibility for
+     * > correctly loading the web component in lazy, non-lazy and CDN builds.
      *
      * @example
-     * This is desirable if you are sure the end user will have these dependencies
-     * available, yet do not wish to declare these as devDependencies for some
-     * technical reasons.
+     * ```ts
+     * // Silence errors for unknown custom elements that start with "fluent-"
+     * silenceUnknownJsxElementUsage: (tagName) => tagName.startsWith("fluent-")
+     * ```
      */
-    readonly externalize?: NonNullable<RollupPluginNodeExternalsOptions>["include"];
+    readonly silenceUnknownJsxElementUsage?: (tagName: string, fileName: string, context: CompilerContext) => boolean;
 };
 export type ServeEnvironmentOptions = {
     /**

package/dist/puppeteerTesting/vitest/matchers/index.d.ts

@@ -1,17 +1,17 @@
 export declare const expectExtend: {
-    toEqualAttribute: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
-    toEqualAttributes: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
-    toEqualText: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
-    toHaveAttribute: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
-    toHaveClass: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
+    toEqualAttribute: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
+    toEqualAttributes: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
+    toEqualText: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
+    toHaveAttribute: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
+    toHaveClass: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
     toHaveClasses: (element: unknown, expectClassNames: string[]) => import('@vitest/expect').SyncExpectationResult;
-    toMatchClasses: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
-    toHaveReceivedEvent: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
-    toHaveReceivedEventTimes: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
-    toHaveReceivedEventDetail: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
-    toHaveFirstReceivedEventDetail: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
-    toHaveLastReceivedEventDetail: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
-    toHaveNthReceivedEventDetail: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState>;
+    toMatchClasses: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
+    toHaveReceivedEvent: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
+    toHaveReceivedEventTimes: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
+    toHaveReceivedEventDetail: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
+    toHaveFirstReceivedEventDetail: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
+    toHaveLastReceivedEventDetail: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
+    toHaveNthReceivedEventDetail: import('@vitest/expect').RawMatcherFn<import('@vitest/expect').MatcherState, any[]>;
 };
 export interface PuppeteerMatchers<R = unknown> {
     toEqualAttribute: (expectedAttribute: string, expectedValue: unknown) => R;

package/dist/testing/vitestTypes.d.ts

@@ -0,0 +1,8 @@
+export type VitestBrowserModeProvider = "playwright" | "preview" | "webdriverio" | (string & {}) | undefined;
+export type VitestPartialConfig = {
+    globalSetup?: string[] | string;
+    runner?: string;
+    include?: string[];
+    environment?: "edge-runtime" | "happy-dom" | "jsdom" | "node" | (Record<never, never> & string);
+    forceRerunTriggers?: string[];
+};

package/dist/transformers/injectRuntimeOptions.d.ts

@@ -1,3 +1,3 @@
-import { SourceDescription } from 'rollup';
 import { CompilerContext } from '../context';
-export declare function injectRuntimeOptions(runtimeTsCode: string, context: CompilerContext): SourceDescription;
+import { TransformResult } from 'vite';
+export declare function injectRuntimeOptions(runtimeTsCode: string, context: CompilerContext): TransformResult;

package/dist/transformers/internalTypeScriptApis.d.ts

@@ -1,5 +1,8 @@
-import { SourceMap } from 'rollup';
 import { default as ts } from 'typescript';
+import { TransformResult } from 'vite';
+type SourceMap = Extract<NonNullable<TransformResult["map"]>, {
+    file: string;
+}>;
 export type UndocumentedTypeScript = {
     readonly createSourceMapGenerator?: (host: ts.CompilerHost, basename: string, sourceRoot: string, dirname: string, compilerOptions: ts.CompilerOptions) => SourceMapGenerator;
     readonly createTextWriter?: (newLine: string) => EmitTextWriter;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arcgis/lumina-compiler",
-  "version": "4.34.0-next.5",
+  "version": "4.34.0-next.50",
   "type": "module",
   "main": "dist/index.js",
   "module": "dist/index.js",
@@ -18,25 +18,28 @@
   ],
   "license": "SEE LICENSE IN LICENSE.md",
   "dependencies": {
-    "@arcgis/api-extractor": "4.34.0-next.5",
-    "@arcgis/components-build-utils": "4.34.0-next.5",
-    "@arcgis/components-utils": "4.34.0-next.5",
-    "chalk": "^5.3.0",
-    "esbuild": "^0.25.4",
-    "glob": "^11.0.0",
-    "js-beautify": "^1.15.1",
-    "mime-types": "^2.1.35",
-    "rollup": "^4.40.2",
-    "rollup-plugin-node-externals": "^8.0.0",
-    "sass-embedded": "^1.79.3",
+    "@arcgis/api-extractor": "4.34.0-next.50",
+    "@arcgis/components-build-utils": "4.34.0-next.50",
+    "@arcgis/components-utils": "4.34.0-next.50",
+    "chalk": "^5.4.1",
+    "esbuild": "^0.25.5",
+    "glob": "^11.0.3",
+    "js-beautify": "^1.15.4",
+    "mime-types": "^3.0.1",
     "tslib": "^2.8.1",
-    "typescript": "~5.8.3",
-    "vite": "^6.3.4",
-    "vite-plugin-dts": "^4.5.3",
-    "vitest": "^3.1.3",
+    "vite-plugin-dts": "^4.5.4",
     "vitest-fail-on-console": "^0.7.1"
   },
   "peerDependencies": {
-    "@arcgis/lumina": "~4.34.0-next.5"
+    "@arcgis/lumina": "~4.34.0-next.50",
+    "lit": "^3.3.0",
+    "typescript": "~5.8.3",
+    "vite": "^7.0.0",
+    "vitest": "^3.2.4"
+  },
+  "peerDependenciesMeta": {
+    "vitest": {
+      "optional": true
+    }
   }
 }

package/dist/jsxToLitHtml/escapeForTemplateLiteral.d.ts

@@ -1,45 +0,0 @@
-/**
- * This file is a workaround for a TypeScript bug:
- * https://github.com/microsoft/TypeScript/issues/59150
- *
- * Once that bug is fixed, the code can be simplified like so:
- * - This file can be removed
- * - For each place where `escapeBackticks` or `escapeForTemplateLiteral` was
- *   used and the result was passed as the 1st AND 2nd parameter to one of
- *   ts.factory.createNoSubstitutionTemplateLiteral,
- *   ts.factory.createTemplateHead, ts.factory.createTemplateMiddle, or
- *   ts.factory.createTemplateTail, change those places like so:
- *   - DO NOT call `escapeBackticks` or `escapeForTemplateLiteral` anymore -
- *     pass the value as is.
- *   - DO NOT provide the 2nd parameter to the factory function.
- * - If `escapeForTemplateLiteral` was used in some other place, it can
- *   potentially be replaced with a function like this:
- *   string=>escapeTemplateSubstitution(string).replaceAll('`','\`')
- *   (where escapeTemplateSubstitution is defined in the current file - move it)
- *
- * More details:
- *
- * In template literals, even though we *really* only need to escape ${ and
- * backticks, we are escaping non-ASCII characters too as that improves scanner
- * performance in JavaScript engines.
- *
- * This is what esbuild does (https://esbuild.github.io/api/#charset), what
- * V8 recommends (https://v8.dev/blog/scanner) and what TypeScript does.
- *
- * The code in this file has been copied from TypeScript's code for escaping
- * template literals (but simplified to remove dead branches and fix eslint
- * warnings):
- * https://github.com/microsoft/TypeScript/blob/3163fe7e3898c1f48cd9bc097b96e3426cd2a453/src/compiler/utilities.ts#L5918-L5986
- *
- * TypeScript can automatically escape template literals for us, but we opt out
- * of that as, due to a bug, they also escape new line characters which is not
- * good as it decreases readability when debugging code.
- *
- * TypeScript does not expose the template literal escaping utils so we had
- * to copy the code here, but modify to not escape new lines.
- *
- */
-declare function escapeNonAsciiString(s: string): string;
-export declare const escapeBackticks: typeof escapeNonAsciiString;
-export declare const escapeTemplateSubstitution: (str: string) => string;
-export {};

package/dist/plugins/buildStencilHydrate.d.ts

@@ -1,16 +0,0 @@
-import { Plugin } from 'vite';
-import { CompilerContext } from '../context';
-/**
- * Emit output compatible with Stencil's dist-hydrate-script build.
- *
- * Based on https://github.com/ionic-team/stencil/blob/main/src/compiler/output-targets/dist-hydrate-script/write-hydrate-outputs.ts
- *
- * @deprecated
- * This option should be used to smooth the migration path from Stencil.
- * You should instruct your SSR users to migrate to Lit's SSR implementation,
- * and then stop using this option.
- *
- * @see https://stenciljs.com/docs/hydrate-app
- * @see https://lit.dev/docs/ssr/overview/
- */
-export declare function buildStencilHydrate(context: CompilerContext): Plugin | undefined;