@mui/internal-benchmark 0.0.3-canary.9 → 0.1.1-canary.0

package/ElementTiming.d.mts

@@ -1,5 +1,6 @@
+import * as React from 'react';
 export declare function ElementTiming({
   name
 }: {
   name: string;
-}): import("react/jsx-runtime").JSX.Element;
+}): React.JSX.Element;

package/Metric.mjs

@@ -33,6 +33,8 @@ function flush(test, accumulator) {
  * tests and loop iterations, inside or outside React.
  */
 export class Metric {
+  name;
+  config;
   constructor(config) {
     this.config = typeof config === 'string' ? {
       name: config

package/index.mjs

@@ -1,5 +1,5 @@
 /**
- * @mui/internal-benchmark v0.0.2
+ * @mui/internal-benchmark v0.1.0
  *
  * @license undefined
  * This source code is licensed under the undefined license found in the
@@ -206,17 +206,15 @@ export function benchmark(name, renderFn, interactionOrOptions, maybeOptions) {
 
     // Paint timings are recorded as one harness-owned `bench:paint` metric: the default sentinel
     // is the base series (`bench:paint`) and named `elementtiming` markers are sub-series
-    // (`bench:paint#grid-header`, …), all sharing a single definition. A default alarm keeps a
-    // >20% paint regression flagged, matching the previous behavior.
+    // (`bench:paint#grid-header`, …), all sharing a single definition. Paint is informational (no
+    // alarm): it dominates each test's total duration, so a per-test paint alarm just duplicates the
+    // Duration regression signal and floods the report on any broadly-regressed run.
     const paint = new ScalarMetric({
       name: 'bench:paint',
       format: {
         style: 'unit',
         unit: 'millisecond',
         maximumFractionDigits: 2
-      },
-      alarm: {
-        error: 0.2
       }
     });
     if (typeof window.gc !== 'function') {
@@ -286,13 +284,13 @@ export function benchmark(name, renderFn, interactionOrOptions, maybeOptions) {
       if (!isWarmup) {
         for (const entry of timing.elementEntries) {
           // Skip paints that happened while recording was paused. Attribute by the paint's
-          // `renderTime`, not by when the observer callback fired (which can lag the paint).
-          if (!recording.activeAt(entry.renderTime)) {
+          // `paintTime`, not by when the observer callback fired (which can lag the paint).
+          if (!recording.activeAt(entry.paintTime)) {
             continue;
           }
           // The default sentinel is the base series; named markers become sub-series.
           const id = entry.identifier === 'default' ? undefined : entry.identifier;
-          paint.record(entry.renderTime - iterationStart, id !== undefined ? {
+          paint.record(entry.paintTime - iterationStart, id !== undefined ? {
             id
           } : undefined);
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mui/internal-benchmark",
-  "version": "0.0.3-canary.9",
+  "version": "0.1.1-canary.0",
   "author": "MUI Team",
   "description": "Benchmark utilities for MUI projects. Internal package.",
   "repository": {
@@ -9,11 +9,11 @@
     "directory": "packages/benchmark"
   },
   "dependencies": {
-    "@babel/runtime": "^7.29.2",
-    "@vitejs/plugin-react": "^6.0.2",
+    "@babel/runtime": "^8.0.5",
+    "@vitejs/plugin-react": "^6.1.1",
     "env-ci": "^11.2.0",
-    "execa": "^9.6.1",
-    "zod": "^4.4.3"
+    "execa": "^10.0.1",
+    "zod": "^4.6.4"
   },
   "peerDependencies": {
     "@vitest/browser-playwright": ">=4.1",
@@ -68,5 +68,5 @@
       }
     }
   },
-  "gitSha": "cb672accc6b61d455e18ce874f99ea841831a734"
+  "gitSha": "764e3b3cfc14293e74e93f3413609025f502bab9"
 }

package/reactRecording.d.mts

@@ -5,7 +5,7 @@ export interface ReactRecordingControls {
   readonly hadEmptyActiveWindow: boolean;
   /**
    * Whether recording was active at `time` (a `performance.now()` timestamp). Paint entries are
-   * observed asynchronously, so they are attributed by their `renderTime` rather than by the
+   * observed asynchronously, so they are attributed by their `paintTime` rather than by the
    * recording state at the moment the observer callback happens to fire.
    */
   activeAt(time: number): boolean;

package/reporter.mjs

@@ -240,6 +240,9 @@ async function loadBaselineReport(baselinePath) {
 class BenchmarkReporter {
   benchmarks = {};
   metricDefinitions = {};
+  outputPath;
+  upload;
+  baselinePath;
   hasFailures = false;
   constructor(options) {
     this.outputPath = options?.outputPath ?? process.env.BENCHMARK_OUTPUT_PATH ?? path.resolve(process.cwd(), 'benchmarks', 'results.json');

package/vitest.mjs

@@ -34,6 +34,18 @@ function resolveViewport(option) {
 // workload needs them.
 const LAUNCH_ARGS = ['--js-flags=--expose-gc', '--disable-background-timer-throttling', '--disable-backgrounding-occluded-windows', '--disable-renderer-backgrounding'];
 export function createBenchmarkVitestConfig(options) {
+  // Benchmarks have to measure production React, which is why the config below sets NODE_ENV to
+  // "production" for the code running in the browser. That alone isn't enough: Vite picks which
+  // JSX runtime to compile against by reading NODE_ENV from the Node process, where Vitest has set
+  // it to "test". Benchmarks then get development JSX calling into a production React build, which
+  // has no `jsxDEV` function, and every benchmark crashes on its first render with
+  // "_jsxDEV is not a function".
+  //
+  // Setting NODE_ENV here, while this config file is still being evaluated, means Vite reads
+  // "production" as well and the two agree. Vitest considers this the intended way to run tests
+  // against production React: https://github.com/vitest-dev/vitest/issues/11265
+  // eslint-disable-next-line mui/consistent-production-guard -- an assignment, not a guard
+  process.env.NODE_ENV = 'production';
   const {
     outputPath,
     baselinePath,