@arcgis/lumina-compiler 4.34.0-next.145 → 4.34.0-next.147

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -37,10 +37,9 @@ export type LuminaOptions = {
37
37
  * For more options, see Vite's "testing" option.
38
38
  * This is equivalent to the `e2e` mode in Stencil.
39
39
  *
40
- * @remarks
41
- * For new projects, we recommend using Vitest browser mode instead of
42
- * Puppeteer. See documentation:
43
- * https://qawebgis.esri.com/components/lumina/testing
40
+ * @deprecated
41
+ * For new projects, use Vitest browser mode instead of Puppeteer.
42
+ * See documentation: https://qawebgis.esri.com/components/lumina/testing
44
43
  */
45
44
  readonly puppeteerTesting?: PuppeteerTestingOptions;
46
45
  /**
@@ -260,9 +259,17 @@ export type DetailedExtraDependency = {
260
259
  */
261
260
  getCdnUrl: (context: CompilerContext) => string;
262
261
  };
262
+ /**
263
+ * @deprecated
264
+ * For new projects, use Vitest browser mode instead of Puppeteer.
265
+ * See documentation: https://qawebgis.esri.com/components/lumina/testing
266
+ */
263
267
  export type PuppeteerTestingOptions = {
264
268
  /**
265
269
  * @default false
270
+ * @deprecated
271
+ * For new projects, use Vitest browser mode instead of Puppeteer.
272
+ * See documentation: https://qawebgis.esri.com/components/lumina/testing
266
273
  */
267
274
  readonly enabled?: boolean;
268
275
  /**
@@ -26,7 +26,7 @@ declare module "vitest" {
26
26
  *
27
27
  * It has to be separate because Vitest's dev server resolves imports for the
28
28
  * "node" import condition. If we instead tell Vitest to use browser export
29
- * conditions, than Lit's "isServer" will be false both in browser and node.js,
29
+ * conditions, then Lit's "isServer" will be false both in browser and node.js,
30
30
  * potentially breaking some components. While happy-dom is neat, it does match
31
31
  * the actual browser API 100%. It is safer to run a separate Vite instance for
32
32
  * Node.js (Vitest) and browser. This is a short-term issue anyway as we are
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@arcgis/lumina-compiler",
3
- "version": "4.34.0-next.145",
3
+ "version": "4.34.0-next.147",
4
4
  "type": "module",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.js",
@@ -18,9 +18,9 @@
18
18
  ],
19
19
  "license": "SEE LICENSE IN LICENSE.md",
20
20
  "dependencies": {
21
- "@arcgis/api-extractor": "4.34.0-next.145",
22
- "@arcgis/components-build-utils": "4.34.0-next.145",
23
- "@arcgis/toolkit": "~4.34.0-next.145",
21
+ "@arcgis/api-extractor": "4.34.0-next.147",
22
+ "@arcgis/components-build-utils": "4.34.0-next.147",
23
+ "@arcgis/toolkit": "~4.34.0-next.147",
24
24
  "chalk": "^5.4.1",
25
25
  "esbuild": "^0.25.5",
26
26
  "glob": "^11.0.3",
@@ -30,7 +30,7 @@
30
30
  "vite-plugin-dts": "^4.5.4"
31
31
  },
32
32
  "peerDependencies": {
33
- "@arcgis/lumina": "~4.34.0-next.145",
33
+ "@arcgis/lumina": "~4.34.0-next.147",
34
34
  "lit": "^3.3.0",
35
35
  "typescript": "~5.8.3",
36
36
  "vite": "^7.0.0",