@arcgis/lumina-compiler 4.34.0-next.3 → 4.34.0-next.31

package/dist/publicTypes.d.ts

@@ -251,6 +251,24 @@ export type DependencyManagementOptions = Omit<RollupPluginNodeExternalsOptions,
      * technical reasons.
      */
     readonly externalize?: NonNullable<RollupPluginNodeExternalsOptions>["include"];
+    /**
+     * 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.
+     *
+     * > [!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
+     * ```ts
+     * // Silence errors for unknown custom elements that start with "fluent-"
+     * silenceUnknownJsxElementUsage: (tagName) => tagName.startsWith("fluent-")
+     * ```
+     */
+    readonly silenceUnknownJsxElementUsage?: (tagName: string, fileName: string, context: CompilerContext) => boolean;
 };
 export type ServeEnvironmentOptions = {
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arcgis/lumina-compiler",
-  "version": "4.34.0-next.3",
+  "version": "4.34.0-next.31",
   "type": "module",
   "main": "dist/index.js",
   "module": "dist/index.js",
@@ -18,9 +18,9 @@
   ],
   "license": "SEE LICENSE IN LICENSE.md",
   "dependencies": {
-    "@arcgis/api-extractor": "4.34.0-next.3",
-    "@arcgis/components-build-utils": "4.34.0-next.3",
-    "@arcgis/components-utils": "4.34.0-next.3",
+    "@arcgis/api-extractor": "4.34.0-next.31",
+    "@arcgis/components-build-utils": "4.34.0-next.31",
+    "@arcgis/components-utils": "4.34.0-next.31",
     "chalk": "^5.3.0",
     "esbuild": "^0.25.4",
     "glob": "^11.0.0",
@@ -37,6 +37,6 @@
     "vitest-fail-on-console": "^0.7.1"
   },
   "peerDependencies": {
-    "@arcgis/lumina": "~4.34.0-next.3"
+    "@arcgis/lumina": "~4.34.0-next.31"
   }
 }

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 {};