@arcgis/lumina-compiler 5.2.0-next.4 → 5.2.0-next.40

package/dist/jsxToLitHtml/config.d.ts

@@ -1,42 +1,25 @@
-export declare const fragmentName = "Fragment";
-export declare const dynamicHtmlTagName = "DynamicHtmlTag";
-export declare const dynamicSvgTagName = "DynamicSvgTag";
-/**
- * Using symbols rather than strings for these so that the type system forces us
- * to handle the dynamic tag name case.
- */
-export declare const dynamicHtmlSymbol: unique symbol;
-export declare const dynamicSvgSymbol: unique symbol;
-/**
- * When Stencil encounters a JSX prop like "onArcgisClick", it converts the
- * first letter of the event name ("ArcgisClick") to lower case, and takes the
- * rest as is ("arcgisClick").
- *
- * But, Preact, React 19 and Lit (Lit JSX in turn) don't do any case
- * conversion so you have to use "onarcgisClick" instead.
- *
- * This means, if you are consuming web component authored in Stencil, it's
- * JSX typings may wrongly include properties like "onArcgisClick" rather
- * than "onarcgisClick".
- *
- * When consuming Stencil typings in a Lit project, we are creating a mapped
- * type that fixes the casing difference. But just in case any place slips
- * through, this flag is used to normalize the casing.
- */
-export declare const shouldNormalizeCustomElementEventCasing = true;
 /**
  * Always set these properties as attributes on all elements
+ *
+ * @internal
  */
-export declare const alwaysAttributes: Set<string>;
+export const alwaysAttributes: Set<string>;
+
 /**
  * Always set these properties as attributes on non-custom-elements
+ *
+ * @internal
  */
-export declare const nativeAlwaysAttributes: Set<string>;
+export const nativeAlwaysAttributes: Set<string>;
+
 /**
  * These don't exist as a property, only as an attribute.
  * Or, the property is read-only, but the attribute is not.
+ *
+ * @internal
  */
-export declare const htmlAlwaysAttributes: Record<string, Set<string> | undefined>;
+export const htmlAlwaysAttributes: Record<string, Set<string> | undefined>;
+
 /**
  * The mappings between native DOM property and the equivalent attribute it
  * reflects to.
@@ -44,81 +27,93 @@ export declare const htmlAlwaysAttributes: Record<string, Set<string> | undefine
  * This list was generated using the ./extractPropertyToAttributeMappings.js
  * script.
  *
+ * @internal
  */
-type PropertyToAttributeMappings = {
-    /**
-     * Mappings that are common to all HTML elements
-     */
-    readonly common: Required<ElementPropertyToAttributeMappings>;
-    /**
-     * Mappings that are specific to a given HTML element
-     */
-    readonly perElement: Record<string, ElementPropertyToAttributeMappings | undefined>;
-};
-export type ElementPropertyToAttributeMappings = {
-    /**
-     * This list is only used to apply an optional performance optimization.
-     * If it gets out of date or is missing some properties, it's not a big deal.
-     *
-     * This list is used to convert JSX properties with static values to
-     * an inlined HTML string that uses the equivalent attribute.
-     *
-     * Thus instead of `.property=${"1"}` final lit-html looks like `attribute=1`.
-     *
-     * Since static attributes are just part of the HTML string and not a special
-     * binding, lit-html doesn't have to waste time diffing them on re-render.
-     */
-    reflected?: Readonly<Record<string, string | undefined>>;
-    /**
-     * Unfortunately, for many DOM **properties**, when set to undefined
-     * (`el.autocapitalize = undefined`), rather than removing the attribute, they
-     * set the attribute to an `"undefined"` string (this is never a desirable
-     * outcome) or some other non-default value. This is the web platform
-     * behavior.
-     *
-     * lit-html also has an anti-feature of rendering `undefined` **attribute**
-     * values as `"undefined"` strings (they wanted to mirror the `.setAttribute()`
-     * behavior).
-     *
-     * Thus, the only way to unset such attributes in lit-html is to use attribute
-     * rather than property, and then add `?? nothing` to the attribute value.
-     * `nothing` is a special magic value Lit had to invent to mean
-     * "removeAttribute()"
-     *
-     * @see https://github.com/lit/lit/issues/4760
-     * @see https://x.com/maxpatiiuk/status/1840567140354798003
-     */
-    stringifiedReflected?: Readonly<Record<string, string | undefined>>;
-    /**
-     * Properties that when set to `undefined` value are actually set to
-     * `"undefined"` string.
-     *
-     * We cannot use `?? nothing` as `nothing` in property bindings acts the same
-     * as `undefined`.
-     *
-     * At the moment, all of these happen to be reset to default value when set
-     * to empty string, thus we add `?? ''` on these if potentially nullish value
-     * was provided.
-     */
-    stringifiedNonReflected?: Readonly<Record<string, "" | undefined>>;
-};
-export declare const propertyToAttributeMappings: PropertyToAttributeMappings;
-export declare const htmlAlwaysBooleanAttributes: Set<string>;
+export interface PropertyToAttributeMappings {
+  /**
+   * Mappings that are common to all HTML elements
+   *
+   * @internal
+   */
+  readonly common: Required<ElementPropertyToAttributeMappings>;
+  /**
+   * Mappings that are specific to a given HTML element
+   *
+   * @internal
+   */
+  readonly perElement: Record<string, ElementPropertyToAttributeMappings | undefined>;
+}
+
+/** @internal */
+export interface ElementPropertyToAttributeMappings {
+  /**
+   * This list is only used to apply an optional performance optimization.
+   * If it gets out of date or is missing some properties, it's not a big deal.
+   *
+   * This list is used to convert JSX properties with static values to
+   * an inlined HTML string that uses the equivalent attribute.
+   *
+   * Thus instead of `.property=${"1"}` final lit-html looks like `attribute=1`.
+   *
+   * Since static attributes are just part of the HTML string and not a special
+   * binding, lit-html doesn't have to waste time diffing them on re-render.
+   *
+   * @internal
+   */
+  reflected?: Readonly<Record<string, string | undefined>>;
+  /**
+   * Unfortunately, for many DOM **properties**, when set to undefined
+   * (`el.autocapitalize = undefined`), rather than removing the attribute, they
+   * set the attribute to an `"undefined"` string (this is never a desirable
+   * outcome) or some other non-default value. This is the web platform
+   * behavior.
+   *
+   * lit-html also has an anti-feature of rendering `undefined` **attribute**
+   * values as `"undefined"` strings (they wanted to mirror the `.setAttribute()`
+   * behavior).
+   *
+   * Thus, the only way to unset such attributes in lit-html is to use attribute
+   * rather than property, and then add `?? nothing` to the attribute value.
+   * `nothing` is a special magic value Lit had to invent to mean
+   * "removeAttribute()"
+   *
+   * @internal
+   * @see https://github.com/lit/lit/issues/4760
+   * @see https://x.com/maxpatiiuk/status/1840567140354798003
+   */
+  stringifiedReflected?: Readonly<Record<string, string | undefined>>;
+  /**
+   * Properties that when set to `undefined` value are actually set to
+   * `"undefined"` string.
+   *
+   * We cannot use `?? nothing` as `nothing` in property bindings acts the same
+   * as `undefined`.
+   *
+   * At the moment, all of these happen to be reset to default value when set
+   * to empty string, thus we add `?? ''` on these if potentially nullish value
+   * was provided.
+   *
+   * @internal
+   */
+  stringifiedNonReflected?: Readonly<Record<string, "" | undefined>>;
+}
+
+/** @internal */
+export const propertyToAttributeMappings: PropertyToAttributeMappings;
+
 /**
  * List of all DOM events settable in JSX. These event names are converted to
  * lowercase. All others are left as authored as we can't make assumptions about
  * what was the intended casing.
- */
-export declare const nativeEvents: Set<string>;
-/**
- * HTML elements that do not have children and closing tags
  *
- * Based on https://developer.mozilla.org/en-US/docs/Glossary/Void_element
+ * @internal
  */
-export declare const voidElements: Set<string>;
+export const nativeEvents: Set<string>;
+
 /**
  * Elements for which the `svg` function needs to be used rather than `html`.
  *
+ * @internal
  * @example
  * ```tsx
  * <svg>
@@ -133,26 +128,12 @@ export declare const voidElements: Set<string>;
  *
  * (foreign elements in HTML can be self-closing)
  */
-export declare const svgElements: Set<string>;
-/**
- * As per the spec, some HTML elements are valid inside of `<svg>`, without
- * being escaped in `<foreignObject>`.
- *
- * For such, it can be ambigous whether `html` or `svg` tag should be used.
- * If ambiguous element has non-ambiguous siblings,
- * jsxChildToTemplateParts will get the tag from them. Otherwise,
- * templatePartsToLitExpression will default to htmlTag, which will
- * probably work fine in all cases.
- *
- * @see https://svgwg.org/svg2-draft/struct.html#SVGElement
- * @see https://github.com/w3c/svgwg/blob/6d756e8e7159822e3e3b723756de6a025190bc68/master/definitions.xml#L281-L282
- * @see https://discord.com/channels/1012791295170859069/1286427223712071692
- *
- */
-export declare const ambiguousHtmlSvgElements: Set<string>;
+export const svgElements: Set<string>;
+
 /**
  * Elements for which the `math` function needs to be used rather than `html`
  *
+ * @internal
  * @example
  * ```tsx
  * <math>
@@ -167,13 +148,4 @@ export declare const ambiguousHtmlSvgElements: Set<string>;
  *
  * (foreign elements in HTML can be self-closing)
  */
-export declare const mathMlElements: Set<string>;
-/**
- * Although most native elements do not contain dashes inside, there are a
- * few exceptions. Explicitly declaring a custom element by this name is
- * forbidden
- *
- * @see https://developer.mozilla.org/en-US/docs/Web/API/CustomElementRegistry/define#valid_custom_element_names
- */
-export declare const blockListedCustomElementNames: Set<string>;
-export {};
+export const mathMlElements: Set<(string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string | string)>;

package/dist/{logger-C9XakOcA.js → logger-edpIalAo.js}

@@ -1,4 +1,4 @@
-import { toSystemPathSeparators as c, path as i } from "@arcgis/components-build-utils";
+import { toSystemPathSeparators as c, path as i } from "@arcgis/node-toolkit/path";
 import { styleText as s } from "node:util";
 let n = {
   // Temporary logger to use until vite config is loaded and we have access to