[code-infra] Add ESLint rules to enforce tree-shakeable production guards for dev-only functions #794

Copilot · 2025-10-07T11:19:57Z

Implementation Summary

Created two ESLint rules to enforce production guards with shared utilities:

Shared Utilities (`nodeEnvUtils.mjs`)

isProcessEnvNodeEnv(node): Checks if a node is process.env.NODE_ENV
isLiteral(node, value): Checks if a node is a Literal with specific value
Reduces code duplication between rules

1. `material-ui/require-dev-wrapper`

Enforces that certain function calls (warnOnce, warn, checkSlot) must be wrapped with tree-shakeable production checks
Only accepts patterns that tree-shake in production:
- ✅ if (process.env.NODE_ENV !== 'production') { devCode() } - tree-shakes
- ✅ if (process.env.NODE_ENV === 'development') { devCode() } - tree-shakes
- ✅ if (process.env.NODE_ENV === 'production') {} else { devCode() } - tree-shakes
- ❌ if (process.env.NODE_ENV === 'production') { devCode() } - does NOT tree-shake!
- ❌ if (process.env.NODE_ENV !== 'test') { devCode() } - does NOT tree-shake reliably
Uses clean logic with currentChild variable for efficient branch detection
Properly handles nested if statements in else blocks
Only validates binary comparisons (no recursive node traversal)
Configurable via options to customize the list of function names
19 comprehensive tests (including nested scenarios)

2. `material-ui/consistent-production-guard`

Enforces consistent patterns for ALL production guard checks using process.env.NODE_ENV
Only allows comparison with the literal string 'production'
Rejects non-statically analyzable constructs (e.g., comparing with variables)
Ensures process.env.NODE_ENV is only used in binary comparisons with === or !==
Uses checkGuard helper to DRY up left/right comparison logic
13 comprehensive tests

These two rules work together but can be enabled independently:

require-dev-wrapper ensures critical dev functions are guarded
consistent-production-guard ensures all production guards follow best practices

The rules help prevent development-only utilities from adding weight to production bundles, addressing issue #207.

Original prompt

@mui/mui-public/issues/207

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

mui-bot · 2025-10-07T11:20:46Z

Bundle size report

Bundle	Parsed size	Gzip size
@base-ui-components/react	0B^(0.00%)	0B^(0.00%)
@mui/x-charts-pro	0B^(0.00%)	0B^(0.00%)

Details of bundle changes

Check out the code infra dashboard for more information about this PR.

Implements a new ESLint rule that enforces certain function calls (warnOnce, warn, checkSlot) to be wrapped with `if (process.env.NODE_ENV !== 'production')` conditional to prevent them from ending up in production bundles. The rule: - Detects calls to specified functions (configurable via options) - Ensures they are wrapped with the correct production check - Catches incorrect conditions (e.g., === instead of !==) - Ignores calls in else blocks of production checks - Includes comprehensive test coverage Co-authored-by: brijeshb42 <[email protected]>

Co-authored-by: brijeshb42 <[email protected]>

Janpot · 2025-10-07T11:37:38Z

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs

+ * checkSlot(key, overrides[k]); // Will trigger error
+ *
+ * @example
+ * // Invalid - wrong condition (=== instead of !==)


This feels wrong to me. I believe what we want is to enforce mutual exclusive checks.

// valid if (process.env.NODE_ENV !== 'production') {} // valid if (process.env.NODE_ENV === 'production') {} // invalid (only compare with production, write !== 'production' instead) if (process.env.NODE_ENV === 'development') {} // invalid (only consider production vs.test) if (process.env.NODE_ENV !== 'test') {} // invalid (not statically analyzable construct) const env = 'production'; if (process.env.NODE_ENV !== env) {} // invalid (not statically analyzable construct) if (foo(process.env.NODE_ENV)) {} // i.e. anything outside a comparison binary operation

@copilot Update the code as per this comment ^

Updated the rule to accept both === and !== comparisons with 'production', while rejecting comparisons with other values like 'development' or 'test', and non-static constructs. Fixed in commit cd90e72.

@copilot Can we instead split this into two rules?

require-dev-wrapper: to detect functions that require a production guard

consistent-production-guard: which make sure these rules are followed:
// valid if (process.env.NODE_ENV !== 'production') {} // valid if (process.env.NODE_ENV === 'production') {} // invalid (only compare with production, write !== 'production' instead) if (process.env.NODE_ENV === 'development') {} // invalid (only consider production vs.test) if (process.env.NODE_ENV !== 'test') {} // invalid (not statically analyzable construct) const env = 'production'; if (process.env.NODE_ENV !== env) {} // invalid (not statically analyzable construct) if (foo(process.env.NODE_ENV)) {} // i.e. anything outside a comparison binary operation

Split into two separate rules as requested:

require-dev-wrapper - Detects functions that need production guards (simplified to only check if wrapped)

consistent-production-guard - Enforces production guard patterns (only 'production' literal, static checks, etc.)

Both rules have comprehensive test coverage and can be enabled independently. Changes in commit 911cf1b.

- Allow both `process.env.NODE_ENV === 'production'` and `!== 'production'` as valid - Only allow comparison with literal 'production' string - Reject comparisons with other environment values ('development', 'test', etc.) - Reject non-statically analyzable constructs (e.g., comparing with variables) - Fix circular reference issue in containsProcessEnvNodeEnv function - Update tests to reflect new behavior (18 tests total) Co-authored-by: brijeshb42 <[email protected]>

Copilot · 2025-10-07T11:49:57Z

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

iojs.org
- Triggering command: curl -q --fail --compressed -L -s REDACTED -o - (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

- Simplified `require-dev-wrapper`: Only checks if functions are wrapped with any production check - New `consistent-production-guard`: Enforces production guard patterns (only 'production' literal, no variables, etc.) - Updated tests for require-dev-wrapper (18 tests) - Added comprehensive tests for consistent-production-guard (13 tests) - Both rules registered in plugin index - All 1388 tests passing Co-authored-by: Janpot <[email protected]>

Copilot · 2025-10-15T12:52:10Z

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

iojs.org
- Triggering command: curl -q --fail --compressed -L -s REDACTED -o - (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

…cc0646

packages/code-infra/src/eslint/material-ui/rules/consistent-production-guard.mjs

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs

- Created shared nodeEnvUtils.mjs with isProcessEnvNodeEnv and isLiteral helpers - Refactored consistent-production-guard to use checkGuard helper (DRY) - Fixed require-dev-wrapper to handle else blocks correctly (valid when if checks for production) - Added test for else block scenario - Simplified error messages by removing nonStaticComparison (combined into invalidComparison) - All 1389 tests passing Co-authored-by: Janpot <[email protected]>

Copilot · 2025-10-15T13:32:11Z

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

iojs.org
- Triggering command: curl -q --fail --compressed -L -s REDACTED -o - (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs

- Changed signature from (left, right, operator, value) to (binaryExpression, operator, value) - Moved logic for checking any NODE_ENV comparison into isNodeEnvComparison when operator is !== - Removed redundant second check in require-dev-wrapper - Simplified code and improved encapsulation - All 1389 tests still passing Co-authored-by: Janpot <[email protected]>

Copilot · 2025-10-15T14:34:12Z

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

iojs.org
- Triggering command: curl -q --fail --compressed -L -s REDACTED -o - (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

packages/code-infra/src/eslint/material-ui/rules/nodeEnvUtils.mjs

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs

…etection - Moved isNodeEnvComparison from nodeEnvUtils.mjs to require-dev-wrapper.mjs (not reused) - Fixed logic: for !== operator, also allow === with any literal value - Simplified branch detection using currentChild variable instead of inner loop - All 1389 tests still passing Co-authored-by: Janpot <[email protected]>

Copilot · 2025-10-15T14:59:11Z

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

iojs.org
- Triggering command: curl -q --fail --compressed -L -s REDACTED -o - (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Janpot · 2025-10-15T15:10:11Z

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs

+      if (
+        operator === '!==' &&
+        binaryExpression.operator === '===' &&
+        ((isProcessEnvNodeEnv(left) && right.type === 'Literal') ||


@copilot is it you not getting it or is it me?

"not equals a certain value" is equivalent to "equals not that value"

Suggested change

((isProcessEnvNodeEnv(left) && right.type === 'Literal') ||

((isProcessEnvNodeEnv(left) && right.type === 'Literal' && right.value !== value) ||

You're absolutely right! Fixed the logic to check right.value !== value to ensure we only accept === comparisons with values that are NOT 'production'.

Fixed in commit ba214aa.

Janpot · 2025-10-15T15:10:46Z

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs

+      }
+
+      // For !== operator in consequent, also allow !== with any other value
+      if (


@copilot remove this, jesus

Removed the unnecessary !== with any value check. The rule now only accepts tree-shakeable patterns.

Fixed in commit ba214aa.

Janpot · 2025-10-15T15:11:46Z

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.test.mjs

+}
+      `,
+    },
+    // Should pass: Function wrapped with === production check


@copilot should not pass, it needs to check that it gets tree shaken away in production

Moved to invalid tests. Code in the then block of === 'production' runs IN production, so it doesn't tree-shake away.

Fixed in commit ba214aa.

Janpot · 2025-10-15T15:12:27Z

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.test.mjs

+}
+      `,
+    },
+    // Should pass: Function wrapped with !== 'test' check (still wrapped)


@copilot Wrong, again, when node env is production, the code shoeuld tree shake away

Removed from valid tests. !== 'test' doesn't reliably tree-shake in production.

Fixed in commit ba214aa.

Janpot · 2025-10-15T15:12:47Z

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.test.mjs

+}
+      `,
+    },
+    // Should pass: Function wrapped with non-static check (still wrapped)


@copilot wrong, irrelevant, remove test

Removed. Non-static comparisons don't tree-shake.

Fixed in commit ba214aa.

Janpot · 2025-10-15T15:13:46Z

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.test.mjs

+}
+      `,
+    },
+    // Should pass: warn wrapped correctly with ===


@copilot wrong, should not pass, this would keep the code in production

Moved to invalid tests. This pattern would execute the dev code IN production.

Fixed in commit ba214aa.

Janpot · 2025-10-15T15:14:57Z

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.test.mjs

+        },
+      ],
+    },
+    // Should fail: Inside else block of production check (!== 'production')


@copilot great, also add the other variant when its in the then block of === 'production'

Added duplicate test case - there were already two tests with the same code in the valid section. The else block test covers this pattern.

Fixed in commit ba214aa.

- Changed logic to only accept patterns that tree-shake in production - Consequent: only !== 'production' or === with non-production values - Alternate (else): only === 'production' - Removed invalid test cases that don't tree-shake - Added invalid tests for patterns that keep code in production - All 1388 tests passing Co-authored-by: Janpot <[email protected]>

Copilot · 2025-10-15T15:25:36Z

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

iojs.org
- Triggering command: curl -q --fail --compressed -L -s REDACTED -o - (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Copilot

Pull Request Overview

This PR introduces two complementary ESLint rules to enforce tree-shakeable production guards and prevent development-only code from ending up in production bundles. The implementation ensures that specific development functions (like warnOnce, warn, and checkSlot) are properly wrapped with production environment checks that will be eliminated during the production build process.

Key Changes:

Added require-dev-wrapper rule to enforce tree-shakeable production guards for specific development functions
Added consistent-production-guard rule to ensure all process.env.NODE_ENV checks follow best practices
Created shared utility functions in nodeEnvUtils.mjs for consistent environment check validation across both rules

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs	Core logic for detecting unwrapped dev functions and validating tree-shakeable patterns
packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.test.mjs	Comprehensive test suite with 18 test cases covering valid/invalid patterns
packages/code-infra/src/eslint/material-ui/rules/consistent-production-guard.mjs	Enforces consistent production guard patterns across all NODE_ENV checks
packages/code-infra/src/eslint/material-ui/rules/consistent-production-guard.test.mjs	Test suite with 13 test cases validating guard pattern enforcement
packages/code-infra/src/eslint/material-ui/rules/nodeEnvUtils.mjs	Shared utilities for AST node validation related to process.env.NODE_ENV
packages/code-infra/src/eslint/material-ui/index.mjs	Registration of both new rules in the material-ui ESLint plugin

Copilot · 2025-10-15T15:47:43Z

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs

+        if (current.type === 'IfStatement') {
+          // Determine which branch we're in
+          const isInConsequent = current.consequent === currentChild;
+          const isInAlternate = current.alternate === currentChild;
+
+          // Skip if not in a branch
+          if (isInConsequent || isInAlternate) {


The condition at line 108 could fail to detect the alternate branch when the alternate is a block statement. When currentChild is a BlockStatement that wraps the actual alternate branch, the reference equality check current.alternate === currentChild will be true. However, the code should also check if currentChild is contained within the alternate branch for nested cases. Consider using a helper function to check if a node is contained within a branch to handle both direct and nested cases.

@copilot Can you come up with a code snippet to prove your point in your previous comment?

The current implementation actually handles this correctly. In JavaScript AST, when you have:

if (process.env.NODE_ENV === 'production') { // some code } else { warnOnce(); // our target node }

The alternate property of the IfStatement directly points to the BlockStatement containing the else clause. As we traverse up from warnOnce(), currentChild will be the BlockStatement, and current.alternate === currentChild will be true.

For nested if statements:

if (process.env.NODE_ENV === 'production') { // some code } else { if (someCondition) { warnOnce(); // our target node } }

When we reach the outer if statement during traversal, currentChild will be the inner IfStatement (not the BlockStatement), so current.alternate === currentChild will still work correctly.

The reference equality check works because we're updating currentChild to be the previous current value in each iteration of the while loop, which maintains the direct parent-child relationship needed for the comparison.

@copilot can you propose a test case for this and add it to the suite?

Added a test case for nested if statements in else blocks. The test verifies that warnOnce inside a nested if statement within the else block of a process.env.NODE_ENV === 'production' check is correctly recognized as wrapped. All 19 tests pass.

Fixed in commit above.

- Added test to verify branch detection works correctly with nested if statements - Tests scenario where warnOnce is in a nested if inside else block of production check - All 19 tests passing including the new test case Co-authored-by: Janpot <[email protected]>

Copilot · 2025-10-23T13:06:05Z

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

iojs.org
- Triggering command: curl -q --fail --compressed -L -s REDACTED -o - (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

…cc0646

Initial plan

1a47091

Copilot AI assigned Copilot and brijeshb42 Oct 7, 2025

Copilot started work on behalf of brijeshb42 October 7, 2025 11:20 View session

Copilot AI and others added 2 commits October 7, 2025 11:29

Add documentation and examples to require-dev-wrapper rule

cd90e72

Co-authored-by: brijeshb42 <[email protected]>

Copilot AI changed the title ~~[WIP] @mui/mui-public/issues/207~~ [code-infra] Add ESLint rule to enforce production guards for dev-only functions Oct 7, 2025

Copilot AI requested a review from brijeshb42 October 7, 2025 11:33

Copilot finished work on behalf of brijeshb42 October 7, 2025 11:33

Janpot reviewed Oct 7, 2025

View reviewed changes

Copilot started work on behalf of brijeshb42 October 7, 2025 11:42 View session

Copilot finished work on behalf of brijeshb42 October 7, 2025 11:50

Copilot started work on behalf of Janpot October 15, 2025 12:42 View session

Copilot AI changed the title ~~[code-infra] Add ESLint rule to enforce production guards for dev-only functions~~ [code-infra] Add ESLint rules to enforce production guards for dev-only functions Oct 15, 2025

Copilot AI requested a review from Janpot October 15, 2025 12:52

Copilot finished work on behalf of Janpot October 15, 2025 12:52

Merge branch 'master' into copilot/fix-19649be1-758d-483e-a6b9-e2b49d…

3650dff

…cc0646

Janpot requested changes Oct 15, 2025

View reviewed changes

packages/code-infra/src/eslint/material-ui/rules/consistent-production-guard.mjs Outdated Show resolved Hide resolved

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs Outdated Show resolved Hide resolved

Copilot started work on behalf of Janpot October 15, 2025 13:23 View session

Copilot AI requested a review from Janpot October 15, 2025 13:32

Copilot finished work on behalf of Janpot October 15, 2025 13:32

Janpot reviewed Oct 15, 2025

View reviewed changes

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs Show resolved Hide resolved

Copilot started work on behalf of Janpot October 15, 2025 14:07 View session

Copilot finished work on behalf of Janpot October 15, 2025 14:26

Copilot AI requested a review from Janpot October 15, 2025 14:26

Copilot started work on behalf of Janpot October 15, 2025 14:27 View session

Copilot finished work on behalf of Janpot October 15, 2025 14:34

Janpot requested changes Oct 15, 2025

View reviewed changes

packages/code-infra/src/eslint/material-ui/rules/nodeEnvUtils.mjs Outdated Show resolved Hide resolved

packages/code-infra/src/eslint/material-ui/rules/require-dev-wrapper.mjs Outdated Show resolved Hide resolved

Copilot started work on behalf of Janpot October 15, 2025 14:50 View session

Copilot finished work on behalf of Janpot October 15, 2025 14:59

Copilot AI requested a review from Janpot October 15, 2025 14:59

zannager added the scope: code-infra Involves the code-infra product (https://www.notion.so/mui-org/5562c14178aa42af97bc1fa5114000cd). label Oct 15, 2025

Janpot requested changes Oct 15, 2025

View reviewed changes

Copilot started work on behalf of Janpot October 15, 2025 15:15 View session

Copilot AI changed the title ~~[code-infra] Add ESLint rules to enforce production guards for dev-only functions~~ [code-infra] Add ESLint rules to enforce tree-shakeable production guards for dev-only functions Oct 15, 2025

Copilot AI requested a review from Janpot October 15, 2025 15:25

Copilot finished work on behalf of Janpot October 15, 2025 15:25

fix manually

ebe83ed

Janpot requested a review from Copilot October 15, 2025 15:46

Copilot AI reviewed Oct 15, 2025

View reviewed changes

Copilot started work on behalf of Janpot October 23, 2025 10:32 View session

Copilot finished work on behalf of Janpot October 23, 2025 10:34

Copilot started work on behalf of Janpot October 23, 2025 12:59 View session

Copilot finished work on behalf of Janpot October 23, 2025 13:06

Merge branch 'master' into copilot/fix-19649be1-758d-483e-a6b9-e2b49d…

25f9303

…cc0646

	((isProcessEnvNodeEnv(left) && right.type === 'Literal') \|\|
	((isProcessEnvNodeEnv(left) && right.type === 'Literal' && right.value !== value) \|\|

[code-infra] Add ESLint rules to enforce tree-shakeable production guards for dev-only functions #794

Are you sure you want to change the base?

[code-infra] Add ESLint rules to enforce tree-shakeable production guards for dev-only functions #794

Conversation

Copilot AI commented Oct 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Implementation Summary

Shared Utilities (nodeEnvUtils.mjs)

1. material-ui/require-dev-wrapper

2. material-ui/consistent-production-guard

Uh oh!

mui-bot commented Oct 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Bundle size report

Uh oh!

Janpot Oct 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Oct 7, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Oct 15, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Oct 7, 2025

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Copilot AI commented Oct 15, 2025

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Uh oh!

Uh oh!

Copilot AI commented Oct 15, 2025

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Uh oh!

Copilot AI commented Oct 15, 2025

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Uh oh!

Uh oh!

Copilot AI commented Oct 15, 2025

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Oct 15, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Oct 15, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Oct 15, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Oct 15, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Oct 15, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Oct 15, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Copilot AI commented Oct 7, 2025 •

edited

Loading

Shared Utilities (`nodeEnvUtils.mjs`)

1. `material-ui/require-dev-wrapper`

2. `material-ui/consistent-production-guard`

mui-bot commented Oct 7, 2025 •

edited

Loading

Janpot Oct 7, 2025 •

edited

Loading