[compiler] Fix error description inconsistency

Small fix to make all descriptions consistently printed with a single period at the end. Ran `grep -rn "description:" packages/babel-plugin-react-compiler/src --include="*.ts" --exclude-dir="__tests__" | grep '\.\s*["\`]'` to find all descriptions ending in a period and manually fixed them.
2025-11-01 09:12:30 +00:00 · 2025-09-06 12:26:52 -04:00
parent df05a6ba6e
commit edc22b833e
116 changed files with 145 additions and 156 deletions
@@ -141,11 +141,10 @@ export class CompilerDiagnostic {
  }

  printErrorMessage(source: string, options: PrintErrorMessageOptions): string {
-    const buffer = [
-      printErrorSummary(this.category, this.reason),
-      '\n\n',
-      this.description,
-    ];
+    const buffer = [printErrorSummary(this.category, this.reason)];
+    if (this.description != null) {
+      buffer.push('\n\n', `${this.description}.`);
+    }
    for (const detail of this.options.details) {
      switch (detail.kind) {
        case 'error': {
@@ -256,7 +256,7 @@ export function addImportsToProgram(
        {
          reason:
            'Encountered conflicting import specifiers in generated program',
-          description: `Conflict from import ${loweredImport.module}:(${loweredImport.imported} as ${loweredImport.name}).`,
+          description: `Conflict from import ${loweredImport.module}:(${loweredImport.imported} as ${loweredImport.name})`,
          details: [
            {
              kind: 'error',
@@ -96,7 +96,7 @@ function assertValidEffectImportReference(
            reason:
              'Cannot infer dependencies of this effect. This will break your build!',
            description:
-              'To resolve, either pass a dependency array or fix reported compiler bailout diagnostics.' +
+              'To resolve, either pass a dependency array or fix reported compiler bailout diagnostics' +
              (maybeErrorDiagnostic ? ` ${maybeErrorDiagnostic}` : ''),
            details: [
              {
@@ -128,9 +128,7 @@ function assertValidFireImportReference(
        reason: '[Fire] Untransformed reference to compiler-required feature.',
        description:
          'Either remove this `fire` call or ensure it is successfully transformed by the compiler' +
-          maybeErrorDiagnostic
-            ? ` ${maybeErrorDiagnostic}`
-            : '',
+          (maybeErrorDiagnostic != null ? ` ${maybeErrorDiagnostic}` : ''),
        details: [
          {
            kind: 'error',
@@ -109,7 +109,7 @@ export function lower(
          CompilerDiagnostic.create({
            category: ErrorCategory.Invariant,
            reason: 'Could not find binding',
-            description: `[BuildHIR] Could not find binding for param \`${param.node.name}\`.`,
+            description: `[BuildHIR] Could not find binding for param \`${param.node.name}\``,
          }).withDetails({
            kind: 'error',
            loc: param.node.loc ?? null,
@@ -173,7 +173,7 @@ export function lower(
        CompilerDiagnostic.create({
          category: ErrorCategory.Todo,
          reason: `Handle ${param.node.type} parameters`,
-          description: `[BuildHIR] Add support for ${param.node.type} parameters.`,
+          description: `[BuildHIR] Add support for ${param.node.type} parameters`,
        }).withDetails({
          kind: 'error',
          loc: param.node.loc ?? null,
@@ -204,7 +204,7 @@ export function lower(
      CompilerDiagnostic.create({
        category: ErrorCategory.Syntax,
        reason: `Unexpected function body kind`,
-        description: `Expected function body to be an expression or a block statement, got \`${body.type}\`.`,
+        description: `Expected function body to be an expression or a block statement, got \`${body.type}\``,
      }).withDetails({
        kind: 'error',
        loc: body.node.loc ?? null,
@@ -460,7 +460,7 @@ export function dropManualMemoization(
                      manualMemo.loadInstr.value.kind === 'PropertyLoad'
                        ? 'React.useMemo'
                        : 'useMemo'
-                    } callback doesn't return a value. useMemo is for computing and caching values, not for arbitrary side effects.`,
+                    } callback doesn't return a value. useMemo is for computing and caching values, not for arbitrary side effects`,
                    suggestions: null,
                  }).withDetails({
                    kind: 'error',
@@ -473,7 +473,7 @@ function applySignature(
            const diagnostic = CompilerDiagnostic.create({
              category: ErrorCategory.Immutability,
              reason: 'This value cannot be modified',
-              description: `${reason}.`,
+              description: reason,
            }).withDetails({
              kind: 'error',
              loc: effect.value.loc,
@@ -1094,7 +1094,7 @@ function applyEffect(
          const diagnostic = CompilerDiagnostic.create({
            category: ErrorCategory.Immutability,
            reason: 'Cannot access variable before it is declared',
-            description: `${variable ?? 'This variable'} is accessed before it is declared, which prevents the earlier access from updating when this value changes over time.`,
+            description: `${variable ?? 'This variable'} is accessed before it is declared, which prevents the earlier access from updating when this value changes over time`,
          });
          if (hoistedAccess != null && hoistedAccess.loc != effect.value.loc) {
            diagnostic.withDetails({
@@ -1133,7 +1133,7 @@ function applyEffect(
          const diagnostic = CompilerDiagnostic.create({
            category: ErrorCategory.Immutability,
            reason: 'This value cannot be modified',
-            description: `${reason}.`,
+            description: reason,
          }).withDetails({
            kind: 'error',
            loc: effect.value.loc,
@@ -2269,7 +2269,7 @@ function computeEffectsForLegacySignature(
          'This API returns functions which cannot be memoized without leading to stale UI. ' +
            'To prevent this, by default React Compiler will skip memoizing this component/hook. ' +
            'However, you may see issues if values from this API are passed to other components/hooks that are ' +
-            'memoized.',
+            'memoized',
        ].join(''),
      }).withDetails({
        kind: 'error',
@@ -83,7 +83,7 @@ class CheckInstructionsAgainstScopesVisitor extends ReactiveFunctionVisitor<
      CompilerError.invariant(false, {
        reason:
          'Encountered an instruction that should be part of a scope, but where that scope has already completed',
-        description: `Instruction [${id}] is part of scope @${scope.id}, but that scope has already completed.`,
+        description: `Instruction [${id}] is part of scope @${scope.id}, but that scope has already completed`,
        details: [
          {
            kind: 'error',
@@ -39,7 +39,7 @@ export function validateLocalsNotReassignedAfterRender(fn: HIRFunction): void {
      CompilerDiagnostic.create({
        category: ErrorCategory.Immutability,
        reason: 'Cannot reassign variable after render completes',
-        description: `Reassigning ${variable} after render has completed can cause inconsistent behavior on subsequent renders. Consider using state instead.`,
+        description: `Reassigning ${variable} after render has completed can cause inconsistent behavior on subsequent renders. Consider using state instead`,
      }).withDetails({
        kind: 'error',
        loc: reassignment.loc,
@@ -59,7 +59,7 @@ export function validateNoCapitalizedCalls(
            CompilerError.throwInvalidReact({
              category: ErrorCategory.CapitalizedCalls,
              reason,
-              description: `${calleeName} may be a component.`,
+              description: `${calleeName} may be a component`,
              loc: value.loc,
              suggestions: null,
            });
@@ -83,7 +83,7 @@ export function validateNoCapitalizedCalls(
            errors.push({
              category: ErrorCategory.CapitalizedCalls,
              reason,
-              description: `${propertyName} may be a component.`,
+              description: `${propertyName} may be a component`,
              loc: value.loc,
              suggestions: null,
            });
@@ -67,7 +67,7 @@ export function validateNoFreezingKnownMutableFunctions(
          CompilerDiagnostic.create({
            category: ErrorCategory.Immutability,
            reason: 'Cannot modify local variables after render completes',
-            description: `This argument is a function which may reassign or mutate ${variable} after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead.`,
+            description: `This argument is a function which may reassign or mutate ${variable} after render, which can cause inconsistent behavior on subsequent renders. Consider using state instead`,
          })
            .withDetails({
              kind: 'error',
@@ -304,7 +304,7 @@ function validateInferredDep(
              errorDiagnostic
                ? getCompareDependencyResultDescription(errorDiagnostic)
                : 'Inferred dependency not present in source'
-            }.`
+            }`
          : '',
      ]
        .join('')
@@ -551,7 +551,7 @@ class Visitor extends ReactiveFunctionVisitor<VisitorState> {
              reason: 'Existing memoization could not be preserved',
              description: [
                'React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. ',
-                'This dependency may be mutated later, which could cause the value to change unexpectedly.',
+                'This dependency may be mutated later, which could cause the value to change unexpectedly',
              ].join(''),
            }).withDetails({
              kind: 'error',
@@ -603,7 +603,7 @@ class Visitor extends ReactiveFunctionVisitor<VisitorState> {
                  category: ErrorCategory.PreserveManualMemo,
                  reason: 'Existing memoization could not be preserved',
                  description: [
-                    'React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. This value was memoized in source but not in compilation output. ',
+                    'React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. This value was memoized in source but not in compilation output',
                    DEBUG
                      ? `${printIdentifier(identifier)} was not memoized.`
                      : '',
@@ -67,7 +67,7 @@ export function validateStaticComponents(
                CompilerDiagnostic.create({
                  category: ErrorCategory.StaticComponents,
                  reason: 'Cannot create components during render',
-                  description: `Components created during render will reset their state each time they are created. Declare components outside of render. `,
+                  description: `Components created during render will reset their state each time they are created. Declare components outside of render`,
                })
                  .withDetails({
                    kind: 'error',
@@ -77,7 +77,7 @@ export function validateUseMemo(fn: HIRFunction): Result<void, CompilerError> {
                category: ErrorCategory.UseMemo,
                reason: 'useMemo() callbacks may not accept parameters',
                description:
-                  'useMemo() callbacks are called by React to cache calculations across re-renders. They should not take parameters. Instead, directly reference the props, state, or local variables needed for the computation.',
+                  'useMemo() callbacks are called by React to cache calculations across re-renders. They should not take parameters. Instead, directly reference the props, state, or local variables needed for the computation',
                suggestions: null,
              }).withDetails({
                kind: 'error',
@@ -94,7 +94,7 @@ export function validateUseMemo(fn: HIRFunction): Result<void, CompilerError> {
                reason:
                  'useMemo() callbacks may not be async or generator functions',
                description:
-                  'useMemo() callbacks are called once and must synchronously return a value.',
+                  'useMemo() callbacks are called once and must synchronously return a value',
                suggestions: null,
              }).withDetails({
                kind: 'error',
@@ -26,7 +26,7 @@ Found 1 error:

 Compilation Skipped: `this` is not supported syntax

-React Compiler does not support compiling functions that use `this`
+React Compiler does not support compiling functions that use `this`.

 error.reserved-words.ts:8:28
   6 |
@@ -19,7 +19,7 @@ Found 1 error:

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `someGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `someGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.assign-global-in-component-tag-function.ts:3:4
  1 | function Component() {
@@ -22,7 +22,7 @@ Found 1 error:

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `someGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `someGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.assign-global-in-jsx-children.ts:3:4
  1 | function Component() {
@@ -20,7 +20,7 @@ Found 1 error:

 Error: React Compiler has skipped optimizing this component because one or more React rule violations were reported by Flow

-React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `$FlowFixMe[react-rule-hook]`
+React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `$FlowFixMe[react-rule-hook]`.

 error.bailout-on-flow-suppression.ts:4:2
  2 |
@@ -23,7 +23,7 @@ Found 2 errors:

 Error: React Compiler has skipped optimizing this component because one or more React ESLint rules were disabled

-React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable my-app/react-rule`
+React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable my-app/react-rule`.

 error.bailout-on-suppression-of-custom-rule.ts:3:0
  1 | // @eslintSuppressionRules:["my-app","react-rule"]
@@ -36,7 +36,7 @@ error.bailout-on-suppression-of-custom-rule.ts:3:0

 Error: React Compiler has skipped optimizing this component because one or more React ESLint rules were disabled

-React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable-next-line my-app/react-rule`
+React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable-next-line my-app/react-rule`.

 error.bailout-on-suppression-of-custom-rule.ts:7:2
   5 |   'use forget';
@@ -31,7 +31,7 @@ Found 1 error:

 Invariant: [InferMutationAliasingEffects] Expected value kind to be initialized

-<unknown> thunk$14
+<unknown> thunk$14.

 error.bug-infer-mutation-aliasing-effects.ts:10:22
   8 |     function thunk(action) {
@@ -18,8 +18,6 @@ Found 1 error:

 Invariant: [Codegen] Internal error: MethodCall::property must be an unpromoted + unmemoized MemberExpression

-
-
 error.bug-invariant-codegen-methodcall.ts:3:17
  1 | const YearsAndMonthsSince = () => {
  2 |   const diff = foo();
@@ -29,7 +29,7 @@ Found 1 error:

 Invariant: Expected consistent kind for destructuring

-Other places were `Reassign` but 'mutate? #t8$46[7:9]{reactive}' is const
+Other places were `Reassign` but 'mutate? #t8$46[7:9]{reactive}' is const.

 error.bug-invariant-expected-consistent-destructuring.ts:9:9
   7 |
@@ -31,7 +31,7 @@ Found 1 error:

 Invariant: Expected all references to a variable to be consistently local or context references

-Identifier <unknown> err$7 is referenced as a context variable, but was previously referenced as a local variable
+Identifier <unknown> err$7 is referenced as a context variable, but was previously referenced as a local variable.

 error.bug-invariant-local-or-context-references.ts:15:13
  13 |     setState(_prevState => ({
@@ -21,8 +21,6 @@ Found 1 error:

 Invariant: Unexpected terminal in optional

-
-
 error.bug-invariant-unexpected-terminal-in-optional.ts:3:16
  1 | const Foo = ({json}) => {
  2 |   try {
@@ -24,7 +24,7 @@ Found 1 error:

 Invariant: Expected temporaries to be promoted to named identifiers in an earlier pass

-identifier 15 is unnamed
+identifier 15 is unnamed.
 ```
          
      
@@ -18,8 +18,6 @@ Found 1 error:

 Invariant: Const declaration cannot be referenced as an expression

-
-
 error.call-args-destructuring-asignment-complex.ts:3:9
  1 | function Component(props) {
  2 |   let x = makeObject();
@@ -18,7 +18,7 @@ Found 1 error:

 Error: Capitalized functions are reserved for components, which must be invoked with JSX. If this is a component, render it with JSX. Otherwise, ensure that it has no hook calls and rename it to begin with a lowercase letter. Alternatively, if you know for a fact that this function is not a component, you can allowlist it via the compiler config

-Bar may be a component..
+Bar may be a component.

 error.capitalized-function-call-aliased.ts:4:2
  2 | function Foo() {
@@ -19,7 +19,7 @@ Found 1 error:

 Error: Capitalized functions are reserved for components, which must be invoked with JSX. If this is a component, render it with JSX. Otherwise, ensure that it has no hook calls and rename it to begin with a lowercase letter. Alternatively, if you know for a fact that this function is not a component, you can allowlist it via the compiler config

-SomeFunc may be a component..
+SomeFunc may be a component.

 error.capitalized-function-call.ts:3:12
  1 | // @validateNoCapitalizedCalls
@@ -19,7 +19,7 @@ Found 1 error:

 Error: Capitalized functions are reserved for components, which must be invoked with JSX. If this is a component, render it with JSX. Otherwise, ensure that it has no hook calls and rename it to begin with a lowercase letter. Alternatively, if you know for a fact that this function is not a component, you can allowlist it via the compiler config

-SomeFunc may be a component..
+SomeFunc may be a component.

 error.capitalized-method-call.ts:3:12
  1 | // @validateNoCapitalizedCalls
@@ -36,7 +36,7 @@ Found 2 errors:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.capture-ref-for-mutation.ts:12:13
  10 |   };
@@ -49,7 +49,7 @@ error.capture-ref-for-mutation.ts:12:13

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.capture-ref-for-mutation.ts:15:13
  13 |   };
@@ -24,7 +24,7 @@ Found 2 errors:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.hook-ref-value.ts:5:23
  3 | function Component(props) {
@@ -37,7 +37,7 @@ error.hook-ref-value.ts:5:23

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.hook-ref-value.ts:5:23
  3 | function Component(props) {
@@ -19,7 +19,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-access-ref-during-render.ts:4:16
  2 | function Component(props) {
@@ -30,7 +30,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-access-ref-in-reducer-init.ts:8:4
   6 |     (state, action) => state + action,
@@ -26,7 +26,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-access-ref-in-reducer.ts:5:29
  3 | function Component(props) {
@@ -22,7 +22,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-access-ref-in-render-mutate-object-with-ref-function.ts:7:19
   5 |   const object = {};
@@ -26,7 +26,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-access-ref-in-state-initializer.ts:5:27
  3 | function Component(props) {
@@ -23,7 +23,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-aliased-ref-in-callback-invoked-during-render-.ts:9:33
   7 |     return <Foo item={item} current={current} />;
@@ -22,7 +22,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

  4 | component Example() {
  5 |   const fooRef = makeObject_Primitives();
@@ -26,7 +26,7 @@ Found 2 errors:

 Error: Calling setState from useMemo may trigger an infinite loop

-Each time the memo callback is evaluated it will change state. This can cause a memoization dependency to change, running the memo function again and causing an infinite loop. Instead of setting state in useMemo(), prefer deriving the value during render. (https://react.dev/reference/react/useState)
+Each time the memo callback is evaluated it will change state. This can cause a memoization dependency to change, running the memo function again and causing an infinite loop. Instead of setting state in useMemo(), prefer deriving the value during render. (https://react.dev/reference/react/useState).

 error.invalid-conditional-setState-in-useMemo.ts:7:6
   5 |   useMemo(() => {
@@ -39,7 +39,7 @@ error.invalid-conditional-setState-in-useMemo.ts:7:6

 Error: Calling setState from useMemo may trigger an infinite loop

-Each time the memo callback is evaluated it will change state. This can cause a memoization dependency to change, running the memo function again and causing an infinite loop. Instead of setting state in useMemo(), prefer deriving the value during render. (https://react.dev/reference/react/useState)
+Each time the memo callback is evaluated it will change state. This can cause a memoization dependency to change, running the memo function again and causing an infinite loop. Instead of setting state in useMemo(), prefer deriving the value during render. (https://react.dev/reference/react/useState).

 error.invalid-conditional-setState-in-useMemo.ts:8:6
   6 |     if (cond) {
@@ -17,7 +17,7 @@ Found 1 error:

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `x` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `x` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.invalid-destructure-assignment-to-global.ts:2:3
  1 | function useFoo(props) {
@@ -19,7 +19,7 @@ Found 1 error:

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `b` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `b` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.invalid-destructure-to-local-global-variables.ts:3:6
  1 | function Component(props) {
@@ -20,7 +20,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-disallow-mutating-ref-in-render.ts:4:2
  2 | function Component() {
@@ -25,7 +25,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-disallow-mutating-refs-in-render-transitive.ts:9:2
   7 |   };
@@ -39,7 +39,7 @@ Found 1 error:

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `someGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `someGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.invalid-global-reassignment-indirect.ts:9:4
   7 |
@@ -21,7 +21,7 @@ Found 3 errors:

 Error: Cannot call impure function during render

-`Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent)
+`Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent).

 error.invalid-impure-functions-in-render.ts:4:15
  2 |
@@ -34,7 +34,7 @@ error.invalid-impure-functions-in-render.ts:4:15

 Error: Cannot call impure function during render

-`performance.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent)
+`performance.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent).

 error.invalid-impure-functions-in-render.ts:5:14
  3 | function Component() {
@@ -47,7 +47,7 @@ error.invalid-impure-functions-in-render.ts:5:14

 Error: Cannot call impure function during render

-`Math.random` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent)
+`Math.random` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent).

 error.invalid-impure-functions-in-render.ts:6:15
  4 |   const date = Date.now();
@@ -19,7 +19,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-pass-ref-to-function.ts:4:16
  2 | function Component(props) {
@@ -18,7 +18,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-read-ref-prop-in-render-destructure.ts:3:16
  1 | // @validateRefAccessDuringRender @compilationMode:"infer"
@@ -18,7 +18,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-read-ref-prop-in-render-property-load.ts:3:16
  1 | // @validateRefAccessDuringRender @compilationMode:"infer"
@@ -29,7 +29,7 @@ Found 1 error:

 Error: Cannot reassign variable in async function

-Reassigning a variable in an async function can cause inconsistent behavior on subsequent renders. Consider using state instead
+Reassigning a variable in an async function can cause inconsistent behavior on subsequent renders. Consider using state instead.

 error.invalid-reassign-local-variable-in-async-callback.ts:8:6
   6 |       // after render, so this should error regardless of where this ends up
@@ -22,7 +22,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-ref-in-callback-invoked-during-render.ts:8:33
   6 |     return <Foo item={item} current={current} />;
@@ -18,7 +18,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-ref-value-as-props.ts:4:19
  2 | function Component(props) {
@@ -19,7 +19,7 @@ Found 2 errors:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-set-and-read-ref-during-render.ts:4:2
  2 | function Component(props) {
@@ -32,7 +32,7 @@ error.invalid-set-and-read-ref-during-render.ts:4:2

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-set-and-read-ref-during-render.ts:5:9
  3 |   const ref = useRef(null);
@@ -19,7 +19,7 @@ Found 2 errors:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-set-and-read-ref-nested-property-during-render.ts:4:2
  2 | function Component(props) {
@@ -32,7 +32,7 @@ error.invalid-set-and-read-ref-nested-property-during-render.ts:4:2

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-set-and-read-ref-nested-property-during-render.ts:5:9
  3 |   const ref = useRef({inner: null});
@@ -30,7 +30,7 @@ Found 1 error:

 Error: Calling setState from useMemo may trigger an infinite loop

-Each time the memo callback is evaluated it will change state. This can cause a memoization dependency to change, running the memo function again and causing an infinite loop. Instead of setting state in useMemo(), prefer deriving the value during render. (https://react.dev/reference/react/useState)
+Each time the memo callback is evaluated it will change state. This can cause a memoization dependency to change, running the memo function again and causing an infinite loop. Instead of setting state in useMemo(), prefer deriving the value during render. (https://react.dev/reference/react/useState).

 error.invalid-setState-in-useMemo-indirect-useCallback.ts:13:4
  11 |
@@ -24,7 +24,7 @@ Found 2 errors:

 Error: Calling setState from useMemo may trigger an infinite loop

-Each time the memo callback is evaluated it will change state. This can cause a memoization dependency to change, running the memo function again and causing an infinite loop. Instead of setting state in useMemo(), prefer deriving the value during render. (https://react.dev/reference/react/useState)
+Each time the memo callback is evaluated it will change state. This can cause a memoization dependency to change, running the memo function again and causing an infinite loop. Instead of setting state in useMemo(), prefer deriving the value during render. (https://react.dev/reference/react/useState).

 error.invalid-setState-in-useMemo.ts:6:4
  4 |
@@ -37,7 +37,7 @@ error.invalid-setState-in-useMemo.ts:6:4

 Error: Calling setState from useMemo may trigger an infinite loop

-Each time the memo callback is evaluated it will change state. This can cause a memoization dependency to change, running the memo function again and causing an infinite loop. Instead of setting state in useMemo(), prefer deriving the value during render. (https://react.dev/reference/react/useState)
+Each time the memo callback is evaluated it will change state. This can cause a memoization dependency to change, running the memo function again and causing an infinite loop. Instead of setting state in useMemo(), prefer deriving the value during render. (https://react.dev/reference/react/useState).

 error.invalid-setState-in-useMemo.ts:7:4
   5 |   useMemo(() => {
@@ -21,7 +21,7 @@ Found 2 errors:

 Error: React Compiler has skipped optimizing this component because one or more React ESLint rules were disabled

-React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable react-hooks/rules-of-hooks`
+React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable react-hooks/rules-of-hooks`.

 error.invalid-sketchy-code-use-forget.ts:1:0
 > 1 | /* eslint-disable react-hooks/rules-of-hooks */
@@ -32,7 +32,7 @@ error.invalid-sketchy-code-use-forget.ts:1:0

 Error: React Compiler has skipped optimizing this component because one or more React ESLint rules were disabled

-React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable-next-line react-hooks/rules-of-hooks`
+React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable-next-line react-hooks/rules-of-hooks`.

 error.invalid-sketchy-code-use-forget.ts:5:2
  3 |   'use forget';
@@ -40,7 +40,7 @@ Found 1 error:

 Error: React Compiler has skipped optimizing this component because one or more React ESLint rules were disabled

-React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable react-hooks/rules-of-hooks`
+React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable react-hooks/rules-of-hooks`.

 error.invalid-unclosed-eslint-suppression.ts:2:0
  1 | // Note: Everything below this is sketchy
@@ -23,7 +23,7 @@ Found 2 errors:

 Error: Calling setState during render may trigger an infinite loop

-Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState)
+Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState).

 error.invalid-unconditional-set-state-in-render.ts:6:2
  4 |   const aliased = setX;
@@ -36,7 +36,7 @@ error.invalid-unconditional-set-state-in-render.ts:6:2

 Error: Calling setState during render may trigger an infinite loop

-Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState)
+Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState).

 error.invalid-unconditional-set-state-in-render.ts:7:2
   5 |
@@ -26,7 +26,7 @@ Found 2 errors:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-use-ref-added-to-dep-without-type-info.ts:10:21
   8 |   // however, this is an instance of accessing a ref during render and is disallowed
@@ -39,7 +39,7 @@ error.invalid-use-ref-added-to-dep-without-type-info.ts:10:21

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-use-ref-added-to-dep-without-type-info.ts:12:28
  10 |   const x = {a, val: val.ref.current};
@@ -21,7 +21,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-write-but-dont-read-ref-in-render.ts:5:2
  3 |   const ref = useRef(null);
@@ -19,7 +19,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.invalid-write-ref-prop-in-render.ts:4:2
  2 | function Component(props) {
@@ -31,7 +31,7 @@ Found 1 error:

 Error: Components and hooks cannot be created dynamically

-The function `Wrapper` appears to be a React component, but it's defined inside `getInput`. Components and Hooks should always be declared at module scope
+The function `Wrapper` appears to be a React component, but it's defined inside `getInput`. Components and Hooks should always be declared at module scope.

 error.nested-component-in-normal-function.ts:2:16
  1 | // @validateNoDynamicallyCreatedComponentsOrHooks
@@ -35,7 +35,7 @@ Found 1 error:

 Error: Components and hooks cannot be created dynamically

-The function `useConfiguredState` appears to be a React hook, but it's defined inside `createCustomHook`. Components and Hooks should always be declared at module scope
+The function `useConfiguredState` appears to be a React hook, but it's defined inside `createCustomHook`. Components and Hooks should always be declared at module scope.

 error.nested-hook-in-normal-function.ts:4:9
  2 | import {useState} from 'react';
@@ -28,7 +28,7 @@ Found 1 error:

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `b` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `b` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.reassign-global-fn-arg.ts:5:4
  3 | export default function MyApp() {
@@ -21,7 +21,7 @@ Found 2 errors:

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `someUnknownGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `someUnknownGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.reassignment-to-global-indirect.ts:4:4
  2 |   const foo = () => {
@@ -34,7 +34,7 @@ error.reassignment-to-global-indirect.ts:4:4

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `moduleLocal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `moduleLocal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.reassignment-to-global-indirect.ts:5:4
  3 |     // Cannot assign to globals
@@ -18,7 +18,7 @@ Found 2 errors:

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `someUnknownGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `someUnknownGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.reassignment-to-global.ts:3:2
  1 | function Component() {
@@ -31,7 +31,7 @@ error.reassignment-to-global.ts:3:2

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `moduleLocal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `moduleLocal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.reassignment-to-global.ts:4:2
  2 |   // Cannot assign to globals
@@ -29,7 +29,7 @@ Found 2 errors:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

   6 | component C() {
   7 |   const r = useRef(DEFAULT_VALUE);
@@ -41,7 +41,7 @@ React refs are values that are not needed for rendering. Refs should only be acc

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

   7 |   const r = useRef(DEFAULT_VALUE);
   8 |   if (r.current == DEFAULT_VALUE) {
@@ -27,7 +27,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

   5 |   const r = useRef(null);
   6 |   if (r.current == null) {
@@ -27,7 +27,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

   5 |   const r = useRef(null);
   6 |   if (r.current == null) {
@@ -28,7 +28,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

   6 |   if (r.current == null) {
   7 |     r.current = 42;
@@ -28,7 +28,7 @@ Found 2 errors:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

  4 | component C() {
  5 |   const r = useRef(null);
@@ -40,7 +40,7 @@ React refs are values that are not needed for rendering. Refs should only be acc

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

   5 |   const r = useRef(null);
   6 |   const guard = r.current == null;
@@ -28,7 +28,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

   6 |   const r2 = useRef(null);
   7 |   if (r.current == null) {
@@ -28,7 +28,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

   7 |     r.current = 1;
   8 |   }
@@ -28,7 +28,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

   7 |     r.current = 1;
   8 |   }
@@ -24,7 +24,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.ref-optional.ts:5:9
  3 | function Component(props) {
@@ -24,7 +24,7 @@ Found 1 error:

 Error: React Compiler has skipped optimizing this component because one or more React ESLint rules were disabled

-React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable-next-line react-hooks/exhaustive-deps`
+React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable-next-line react-hooks/exhaustive-deps`.

 error.sketchy-code-exhaustive-deps.ts:6:7
  4 |     () => {
@@ -25,7 +25,7 @@ Found 1 error:

 Error: React Compiler has skipped optimizing this component because one or more React ESLint rules were disabled

-React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable react-hooks/rules-of-hooks`
+React Compiler only works when your components follow all the rules of React, disabling them may result in unexpected or incorrect behavior. Found suppression `eslint-disable react-hooks/rules-of-hooks`.

 error.sketchy-code-rules-of-hooks.ts:1:0
 > 1 | /* eslint-disable react-hooks/rules-of-hooks */
@@ -26,8 +26,6 @@ Found 1 error:

 Invariant: [Codegen] Internal error: MethodCall::property must be an unpromoted + unmemoized MemberExpression

-
-
 error.todo-nested-method-calls-lower-property-load-into-temporary.ts:6:14
  4 | function Component({}) {
  5 |   const items = makeArray(0, 1, 2, null, 4, false, 6);
@@ -23,7 +23,7 @@ Found 1 error:

 Invariant: [InferMutationAliasingEffects] Expected value kind to be initialized

-<unknown> hasErrors_0$15:TFunction
+<unknown> hasErrors_0$15:TFunction.

 error.todo-repro-named-function-with-shadowed-local-same-name.ts:9:9
   7 |     return hasErrors;
@@ -35,7 +35,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.todo-useCallback-set-ref-nested-property-ref-modified-later-preserve-memoization.ts:14:2
  12 |
@@ -26,7 +26,7 @@ Found 1 error:

 Error: Calling setState during render may trigger an infinite loop

-Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState)
+Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState).

 error.unconditional-set-state-in-render-after-loop-break.ts:11:2
   9 |     }
@@ -21,7 +21,7 @@ Found 1 error:

 Error: Calling setState during render may trigger an infinite loop

-Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState)
+Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState).

 error.unconditional-set-state-in-render-after-loop.ts:6:2
  4 |   for (const _ of props) {
@@ -26,7 +26,7 @@ Found 1 error:

 Error: Calling setState during render may trigger an infinite loop

-Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState)
+Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState).

 error.unconditional-set-state-in-render-with-loop-throw.ts:11:2
   9 |     }
@@ -24,7 +24,7 @@ Found 1 error:

 Error: Calling setState during render may trigger an infinite loop

-Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState)
+Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState).

 error.unconditional-set-state-lambda.ts:8:2
   6 |     setX(1);
@@ -32,7 +32,7 @@ Found 1 error:

 Error: Calling setState during render may trigger an infinite loop

-Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState)
+Calling setState during render will trigger another render, and can lead to infinite loops. (https://react.dev/reference/react/useState).

 error.unconditional-set-state-nested-function-expressions.ts:16:2
  14 |     bar();
@@ -23,7 +23,7 @@ Found 1 error:

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `renderCount` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `renderCount` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.update-global-should-bailout.ts:3:2
  1 | let renderCount = 0;
@@ -38,7 +38,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.useCallback-accesses-ref-mutated-later-via-function-preserve-memoization.ts:17:2
  15 |     ref.current.inner = null;
@@ -34,7 +34,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.useCallback-set-ref-nested-property-dont-preserve-memoization.ts:13:2
  11 |   });
@@ -32,7 +32,7 @@ Found 1 error:

 Error: Expected the dependency list for useMemo to be an array literal

-Expected the dependency list for useMemo to be an array literal
+Expected the dependency list for useMemo to be an array literal.

 error.useMemo-non-literal-depslist.ts:10:4
   8 |       return text.toUpperCase();
@@ -24,7 +24,7 @@ Found 1 error:

 Error: Cannot access refs during render

-React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef)
+React refs are values that are not needed for rendering. Refs should only be accessed outside of render, such as in event handlers or effects. Accessing a ref value (the `current` property) during render can cause your component not to update as expected (https://react.dev/reference/react/useRef).

 error.validate-mutate-ref-arg-in-render.ts:3:14
  1 | // @validateRefAccessDuringRender:true
@@ -54,7 +54,7 @@ Found 1 error:

 Todo: Support local variables named `fbt`

-Local variables named `fbt` may conflict with the fbt plugin and are not yet supported
+Local variables named `fbt` may conflict with the fbt plugin and are not yet supported.

 error.todo-fbt-as-local.ts:18:19
  16 |
@@ -23,7 +23,7 @@ Found 1 error:

 Todo: Support duplicate fbt tags

-Support `<fbt>` tags with multiple `<fbt:enum>` values
+Support `<fbt>` tags with multiple `<fbt:enum>` values.

 error.todo-fbt-unknown-enum-value.ts:6:7
  4 |   return (
@@ -18,7 +18,7 @@ Found 1 error:

 Todo: Support local variables named `fbt`

-Local variables named `fbt` may conflict with the fbt plugin and are not yet supported
+Local variables named `fbt` may conflict with the fbt plugin and are not yet supported.

 error.todo-locally-require-fbt.ts:2:8
  1 | function Component(props) {
@@ -57,7 +57,7 @@ Found 1 error:

 Todo: Support duplicate fbt tags

-Support `<fbt>` tags with multiple `<fbt:plural>` values
+Support `<fbt>` tags with multiple `<fbt:plural>` values.

 error.todo-multiple-fbt-plural.ts:29:7
  27 |   return (
@@ -58,7 +58,7 @@ export const FIXTURE_ENTRYPOINT = {
 ## Logs

 ```
-{"kind":"CompileError","fnLoc":{"start":{"line":6,"column":0,"index":206},"end":{"line":16,"column":1,"index":433},"filename":"dynamic-gating-bailout-nopanic.ts"},"detail":{"options":{"category":"PreserveManualMemo","reason":"Existing memoization could not be preserved","description":"React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. The inferred dependencies did not match the manually specified dependencies, which could cause the value to change more or less frequently than expected. The inferred dependency was `value`, but the source dependencies were []. Inferred dependency not present in source.","suggestions":null,"details":[{"kind":"error","loc":{"start":{"line":9,"column":31,"index":288},"end":{"line":9,"column":52,"index":309},"filename":"dynamic-gating-bailout-nopanic.ts"},"message":"Could not preserve existing manual memoization"}]}}}
+{"kind":"CompileError","fnLoc":{"start":{"line":6,"column":0,"index":206},"end":{"line":16,"column":1,"index":433},"filename":"dynamic-gating-bailout-nopanic.ts"},"detail":{"options":{"category":"PreserveManualMemo","reason":"Existing memoization could not be preserved","description":"React Compiler has skipped optimizing this component because the existing manual memoization could not be preserved. The inferred dependencies did not match the manually specified dependencies, which could cause the value to change more or less frequently than expected. The inferred dependency was `value`, but the source dependencies were []. Inferred dependency not present in source","suggestions":null,"details":[{"kind":"error","loc":{"start":{"line":9,"column":31,"index":288},"end":{"line":9,"column":52,"index":309},"filename":"dynamic-gating-bailout-nopanic.ts"},"message":"Could not preserve existing manual memoization"}]}}}
 ```
      
 ### Eval output
@@ -36,7 +36,7 @@ Found 1 error:

 Error: Cannot infer dependencies of this effect. This will break your build!

-To resolve, either pass a dependency array or fix reported compiler bailout diagnostics. Todo: (BuildHIR::lowerStatement) Handle TryStatement without a catch clause (13:6)
+To resolve, either pass a dependency array or fix reported compiler bailout diagnostics Todo: (BuildHIR::lowerStatement) Handle TryStatement without a catch clause (13:6).

 error.todo-syntax.ts:11:2
   9 | function Component({prop1}) {
@@ -48,7 +48,7 @@ export const FIXTURE_ENTRYPOINT = {
 ## Logs

 ```
-{"kind":"CompileError","fnLoc":{"start":{"line":5,"column":0,"index":149},"end":{"line":12,"column":1,"index":404},"filename":"mutate-after-useeffect-optional-chain.ts"},"detail":{"options":{"category":"Immutability","reason":"This value cannot be modified","description":"Modifying a value used previously in an effect function or as an effect dependency is not allowed. Consider moving the modification before calling useEffect().","details":[{"kind":"error","loc":{"start":{"line":10,"column":2,"index":365},"end":{"line":10,"column":5,"index":368},"filename":"mutate-after-useeffect-optional-chain.ts","identifierName":"arr"},"message":"value cannot be modified"}]}}}
+{"kind":"CompileError","fnLoc":{"start":{"line":5,"column":0,"index":149},"end":{"line":12,"column":1,"index":404},"filename":"mutate-after-useeffect-optional-chain.ts"},"detail":{"options":{"category":"Immutability","reason":"This value cannot be modified","description":"Modifying a value used previously in an effect function or as an effect dependency is not allowed. Consider moving the modification before calling useEffect()","details":[{"kind":"error","loc":{"start":{"line":10,"column":2,"index":365},"end":{"line":10,"column":5,"index":368},"filename":"mutate-after-useeffect-optional-chain.ts","identifierName":"arr"},"message":"value cannot be modified"}]}}}
 {"kind":"AutoDepsDecorations","fnLoc":{"start":{"line":9,"column":2,"index":314},"end":{"line":9,"column":49,"index":361},"filename":"mutate-after-useeffect-optional-chain.ts"},"decorations":[{"start":{"line":9,"column":24,"index":336},"end":{"line":9,"column":27,"index":339},"filename":"mutate-after-useeffect-optional-chain.ts","identifierName":"arr"}]}
 {"kind":"CompileSuccess","fnLoc":{"start":{"line":5,"column":0,"index":149},"end":{"line":12,"column":1,"index":404},"filename":"mutate-after-useeffect-optional-chain.ts"},"fnName":"Component","memoSlots":0,"memoBlocks":0,"memoValues":0,"prunedMemoBlocks":0,"prunedMemoValues":0}
 ```
@@ -47,7 +47,7 @@ export const FIXTURE_ENTRYPOINT = {
 ## Logs

 ```
-{"kind":"CompileError","fnLoc":{"start":{"line":4,"column":0,"index":111},"end":{"line":11,"column":1,"index":242},"filename":"mutate-after-useeffect.ts"},"detail":{"options":{"category":"Immutability","reason":"This value cannot be modified","description":"Modifying a value used previously in an effect function or as an effect dependency is not allowed. Consider moving the modification before calling useEffect().","details":[{"kind":"error","loc":{"start":{"line":9,"column":2,"index":214},"end":{"line":9,"column":5,"index":217},"filename":"mutate-after-useeffect.ts","identifierName":"arr"},"message":"value cannot be modified"}]}}}
+{"kind":"CompileError","fnLoc":{"start":{"line":4,"column":0,"index":111},"end":{"line":11,"column":1,"index":242},"filename":"mutate-after-useeffect.ts"},"detail":{"options":{"category":"Immutability","reason":"This value cannot be modified","description":"Modifying a value used previously in an effect function or as an effect dependency is not allowed. Consider moving the modification before calling useEffect()","details":[{"kind":"error","loc":{"start":{"line":9,"column":2,"index":214},"end":{"line":9,"column":5,"index":217},"filename":"mutate-after-useeffect.ts","identifierName":"arr"},"message":"value cannot be modified"}]}}}
 {"kind":"AutoDepsDecorations","fnLoc":{"start":{"line":6,"column":2,"index":159},"end":{"line":8,"column":14,"index":210},"filename":"mutate-after-useeffect.ts"},"decorations":[{"start":{"line":7,"column":4,"index":181},"end":{"line":7,"column":7,"index":184},"filename":"mutate-after-useeffect.ts","identifierName":"arr"},{"start":{"line":7,"column":4,"index":181},"end":{"line":7,"column":7,"index":184},"filename":"mutate-after-useeffect.ts","identifierName":"arr"},{"start":{"line":7,"column":13,"index":190},"end":{"line":7,"column":16,"index":193},"filename":"mutate-after-useeffect.ts","identifierName":"foo"}]}
 {"kind":"CompileSuccess","fnLoc":{"start":{"line":4,"column":0,"index":111},"end":{"line":11,"column":1,"index":242},"filename":"mutate-after-useeffect.ts"},"fnName":"Component","memoSlots":0,"memoBlocks":0,"memoValues":0,"prunedMemoBlocks":0,"prunedMemoValues":0}
 ```
@@ -54,7 +54,7 @@ export const FIXTURE_ENTRYPOINT = {
 ## Logs

 ```
-{"kind":"CompileError","fnLoc":{"start":{"line":6,"column":0,"index":195},"end":{"line":14,"column":1,"index":409},"filename":"retry-no-emit.ts"},"detail":{"options":{"category":"Immutability","reason":"This value cannot be modified","description":"Modifying a value previously passed as an argument to a hook is not allowed. Consider moving the modification before calling the hook.","details":[{"kind":"error","loc":{"start":{"line":12,"column":2,"index":372},"end":{"line":12,"column":6,"index":376},"filename":"retry-no-emit.ts","identifierName":"arr2"},"message":"value cannot be modified"}]}}}
+{"kind":"CompileError","fnLoc":{"start":{"line":6,"column":0,"index":195},"end":{"line":14,"column":1,"index":409},"filename":"retry-no-emit.ts"},"detail":{"options":{"category":"Immutability","reason":"This value cannot be modified","description":"Modifying a value previously passed as an argument to a hook is not allowed. Consider moving the modification before calling the hook","details":[{"kind":"error","loc":{"start":{"line":12,"column":2,"index":372},"end":{"line":12,"column":6,"index":376},"filename":"retry-no-emit.ts","identifierName":"arr2"},"message":"value cannot be modified"}]}}}
 {"kind":"AutoDepsDecorations","fnLoc":{"start":{"line":8,"column":2,"index":248},"end":{"line":8,"column":46,"index":292},"filename":"retry-no-emit.ts"},"decorations":[{"start":{"line":8,"column":31,"index":277},"end":{"line":8,"column":34,"index":280},"filename":"retry-no-emit.ts","identifierName":"arr"}]}
 {"kind":"AutoDepsDecorations","fnLoc":{"start":{"line":11,"column":2,"index":316},"end":{"line":11,"column":54,"index":368},"filename":"retry-no-emit.ts"},"decorations":[{"start":{"line":11,"column":25,"index":339},"end":{"line":11,"column":29,"index":343},"filename":"retry-no-emit.ts","identifierName":"arr2"},{"start":{"line":11,"column":25,"index":339},"end":{"line":11,"column":29,"index":343},"filename":"retry-no-emit.ts","identifierName":"arr2"},{"start":{"line":11,"column":35,"index":349},"end":{"line":11,"column":42,"index":356},"filename":"retry-no-emit.ts","identifierName":"propVal"}]}
 {"kind":"CompileSuccess","fnLoc":{"start":{"line":6,"column":0,"index":195},"end":{"line":14,"column":1,"index":409},"filename":"retry-no-emit.ts"},"fnName":"Foo","memoSlots":0,"memoBlocks":0,"memoValues":0,"prunedMemoBlocks":0,"prunedMemoValues":0}
@@ -21,7 +21,7 @@ Found 3 errors:

 Error: Cannot call impure function during render

-`Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent)
+`Date.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent).

 error.invalid-impure-functions-in-render.ts:4:15
  2 |
@@ -34,7 +34,7 @@ error.invalid-impure-functions-in-render.ts:4:15

 Error: Cannot call impure function during render

-`performance.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent)
+`performance.now` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent).

 error.invalid-impure-functions-in-render.ts:5:14
  3 | function Component() {
@@ -47,7 +47,7 @@ error.invalid-impure-functions-in-render.ts:5:14

 Error: Cannot call impure function during render

-`Math.random` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent)
+`Math.random` is an impure function. Calling an impure function can produce unstable results that update unpredictably when the component happens to re-render. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#components-and-hooks-must-be-idempotent).

 error.invalid-impure-functions-in-render.ts:6:15
  4 |   const date = Date.now();
@@ -22,7 +22,7 @@ Found 2 errors:

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `someUnknownGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `someUnknownGlobal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.reassignment-to-global-indirect.ts:5:4
  3 |   const foo = () => {
@@ -35,7 +35,7 @@ error.reassignment-to-global-indirect.ts:5:4

 Error: Cannot reassign variables declared outside of the component/hook

-Variable `moduleLocal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render)
+Variable `moduleLocal` is declared outside of the component/hook. Reassigning this value during render is a form of side effect, which can cause unpredictable behavior depending on when the component happens to re-render. If this variable is used in rendering, use useState instead. Otherwise, consider updating it in an effect. (https://react.dev/reference/rules/components-and-hooks-must-be-pure#side-effects-must-run-outside-of-render).

 error.reassignment-to-global-indirect.ts:6:4
  4 |     // Cannot assign to globals
--- a/Show More
+++ b/Show More