26,417 matches across 25 files for error
snippet_mode: grep · sorted by relevance
14 "permissions": {
15 "allow": [
16▶ "Skill(extract-errors)",
17 "Skill(feature-flags)",
18 "Skill(fix)",
· · ·
30 "Bash(yarn prettier:*)",
31 "Bash(yarn build:*)",
32▶ "Bash(yarn extract-errors:*)",
33 "Bash(yarn flags:*)"
34 ],
1---
2▶name: extract-errors
3description: Use when adding new error messages to React, or seeing "unknown error code" warnings.
4---
· · ·
3▶description: Use when adding new error messages to React, or seeing "unknown error code" warnings.
4---
5
· · ·
6▶# Extract Error Codes
7
8## Instructions
· · ·
9
10▶1. Run `yarn extract-errors`
112. Report if any new errors need codes assigned
123. Check if error codes are up to date
· · ·
11▶2. Report if any new errors need codes assigned
123. Check if error codes are up to date
13
+ 1 more matches in this file
1---
2name: fix
3▶description: Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.
4---
5
· · ·
15
16- **Running prettier on wrong files** - `yarn prettier` only formats changed files
17▶- **Ignoring linc errors** - These will fail CI, fix them before committing
18
1---
2name: flow
3▶description: Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
4---
5
· · ·
21
221. Run `yarn flow $ARGUMENTS` (use `dom-node` if no argument)
23▶2. Report type errors with file locations
243. For comprehensive checking (slow), use `yarn flow-ci`
25
21packages/react-devtools-extensions/firefox/build
22packages/react-devtools-extensions/shared/build
23▶packages/react-devtools-extensions/src/ErrorTesterCompiled.js
24packages/react-devtools-fusebox/dist
25packages/react-devtools-inline/dist
10const OFF = 0;
11const WARNING = 1;
12▶const ERROR = 2;
13
14module.exports = {
· · ·
42 'ft-flow/array-style-complex-type': [OFF, 'verbose'],
43 'ft-flow/array-style-simple-type': [OFF, 'verbose'], // TODO should be WARNING
44▶ 'ft-flow/boolean-style': ERROR,
45 'ft-flow/no-dupe-keys': ERROR,
46 'ft-flow/no-primitive-constructor-types': ERROR,
· · ·
45▶ 'ft-flow/no-dupe-keys': ERROR,
46 'ft-flow/no-primitive-constructor-types': ERROR,
47 'ft-flow/no-types-missing-file-annotation': OFF, // TODO should be ERROR
· · ·
46▶ 'ft-flow/no-primitive-constructor-types': ERROR,
47 'ft-flow/no-types-missing-file-annotation': OFF, // TODO should be ERROR
48 'ft-flow/no-unused-expressions': ERROR,
· · ·
47▶ 'ft-flow/no-types-missing-file-annotation': OFF, // TODO should be ERROR
48 'ft-flow/no-unused-expressions': ERROR,
49 // 'ft-flow/no-weak-types': WARNING,
+ 85 more matches in this file
10 Which website or app were you using when the bug happened?
11
12▶ This should be a public URL, GitHub repo, or Code Sandbox app so the React team can reproduce the error being reported. (Please no localhost URLs.)
13 placeholder: |
14 e.g. website URL, public GitHub repo, or Code Sandbox app
· · ·
54 Please do not edit this field.
55- type: input
56▶ id: automated_error_message
57 attributes:
58 label: Error message (automated)
· · ·
58▶ label: Error message (automated)
59 description: |
60 Please do not edit this field.
· · ·
62 id: automated_call_stack
63 attributes:
64▶ label: Error call stack (automated)
65 description: |
66 Please do not edit this field.
· · ·
69 id: automated_component_stack
70 attributes:
71▶ label: Error component stack (automated)
72 description: |
73 Please do not edit this field.
53 name: build
54 path: build
55▶ if-no-files-found: error
56
57 build_devtools_and_process_artifacts:
· · ·
90 name: react-devtools
91 path: build/devtools
92▶ if-no-files-found: error
93 # Simplifies getting the extension for local testing
94 - name: Archive chrome extension
· · ·
97 name: react-devtools-chrome-extension
98 path: build/devtools/chrome-extension.zip
99▶ if-no-files-found: error
100 - name: Archive firefox extension
101 uses: actions/upload-artifact@v4
· · ·
103 name: react-devtools-firefox-extension
104 path: build/devtools/firefox-extension.zip
105▶ if-no-files-found: error
106
107 run_devtools_tests_for_versions:
313 name: _build_${{ matrix.worker_id }}_${{ matrix.release_channel }}
314 path: build
315▶ if-no-files-found: error
316
317 test_build:
· · ·
487 ./build.tgz
488 ./build2.tgz
489▶ if-no-files-found: error
490 - uses: actions/attest-build-provenance@v2
491 # We don't verify builds generated from pull requests not originating from react/react.
· · ·
500 subject-digest: sha256:${{ steps.upload_artifacts_combined.outputs.artifact-digest }}
501
502▶ check_error_codes:
503 name: Search build artifacts for unminified errors
504 needs: [build_and_lint, runtime_node_modules_cache]
· · ·
503▶ name: Search build artifacts for unminified errors
504 needs: [build_and_lint, runtime_node_modules_cache]
505 runs-on: ubuntu-latest
· · ·
531 - name: Display structure of build
532 run: ls -R build
533▶ - name: Search build artifacts for unminified errors
534 run: |
535 yarn extract-errors
+ 3 more matches in this file
61 name: build
62 path: build/
63▶ if-no-files-found: error
64
65
· · ·
200 name: compiled
201 path: compiled/
202▶ if-no-files-found: error
203 - uses: actions/upload-artifact@v4
204 with:
· · ·
205 name: compiled-rn
206 path: compiled-rn/
207▶ if-no-files-found: error
208
209 commit_www_artifacts:
· · ·
380 const PATTERN = new RegExp(`${GENERATED} (?:SignedSource<<([a-f0-9]{32})>>)`);
381
382▶ const TokenNotFoundError = new Error(
383 `SignedSource.signFile(...): Cannot sign file without token: ${NEWTOKEN}`
384 );
· · ·
403 data = data.replace(PATTERN, SignedSource.getSigningToken());
404 } else {
405▶ throw TokenNotFoundError;
406 }
407 }
+ 2 more matches in this file
42 });
43 if (res.status !== 200) {
44▶ console.error(res);
45 throw new Error('Unable to fetch MAINTAINERS file');
46 }
· · ·
45▶ throw new Error('Unable to fetch MAINTAINERS file');
46 }
47 content = Buffer.from(res.data.content, 'base64').toString();
· · ·
48 if (content == null || typeof content !== 'string') {
49▶ throw new Error('Unable to retrieve MAINTAINERS file');
50 }
51
7packages/react-devtools-extensions/edge/build
8packages/react-devtools-extensions/shared/build
9▶packages/react-devtools-extensions/src/ErrorTesterCompiled.js
10packages/react-devtools-fusebox/dist
11packages/react-devtools-inline/dist
· · ·
21compiler/**/.next
22
23▶# contains invalid graphql`...` which results in a promise rejection error from `yarn prettier-all`.
24compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/error.todo-kitchensink.js
25# contains invalid const reassignment; the fixture asserts the compiler diagnostic.
· · ·
24▶compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/error.todo-kitchensink.js
25# contains invalid const reassignment; the fixture asserts the compiler diagnostic.
26compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/error.invalid-reassign-const.js
· · ·
26▶compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/error.invalid-reassign-const.js
27# preserves the exact sequence-expression source shape used by the fixture.
28compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/memoize-value-block-value-sequence.js
40- `<Activity />` was developed over many years, starting before `ClassComponent.setState` (@acdlite @sebmarkbage and many others)
41- Stringify context as "SomeContext" instead of "SomeContext.Provider" (@kassens [#33507](https://github.com/facebook/react/pull/33507))
42▶- Include stack of cause of React instrumentation errors with `%o` placeholder (@eps1lon [#34198](https://github.com/facebook/react/pull/34198))
43- Fix infinite `useDeferredValue` loop in popstate event (@acdlite [#32821](https://github.com/facebook/react/pull/32821))
44- Fix a bug when an initial value was passed to `useDeferredValue` (@acdlite [#34376](https://github.com/facebook/react/pull/34376))
· · ·
56- Allow `nonce` to be used on hoistable styles (@Andarist [#32461](https://github.com/facebook/react/pull/32461))
57- Warn for using a React owned node as a Container if it also has text content (@sebmarkbage [#32774](https://github.com/facebook/react/pull/32774))
58▶- s/HTML/text for for error messages if text hydration mismatches (@rickhanlonii [#32763](https://github.com/facebook/react/pull/32763))
59- Fix a bug with `React.use` inside `React.lazy`\-ed Component (@hi-ogawa [#33941](https://github.com/facebook/react/pull/33941))
60- Enable the `progressiveChunkSize` option for server-side-rendering APIs (@sebmarkbage [#33027](https://github.com/facebook/react/pull/33027))
· · ·
66
67- Preload `<img>` and `<link>` using hints before they're rendered (@sebmarkbage [#34604](https://github.com/facebook/react/pull/34604))
68▶- Log error if production elements are rendered during development (@eps1lon [#34189](https://github.com/facebook/react/pull/34189))
69- Fix a bug when returning a Temporary reference (e.g. a Client Reference) from Server Functions (@sebmarkbage [#34084](https://github.com/facebook/react/pull/34084), @denk0403 [#33761](https://github.com/facebook/react/pull/33761))
70- Pass line/column to `filterStackFrame` (@eps1lon [#33707](https://github.com/facebook/react/pull/33707))
· · ·
93### Owner Stack
94
95▶An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.
96
97* An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
· · ·
97▶* An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
98* The [captureOwnerStack API](https://react.dev/reference/react/captureOwnerStack) is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. [#29923](https://github.com/facebook/react/pull/29923), [#32353](https://github.com/facebook/react/pull/32353), [#30306](https://github.com/facebook/react/pull/30306),
99[#32538](https://github.com/facebook/react/pull/32538), [#32529](https://github.com/facebook/react/pull/32529), [#32538](https://github.com/facebook/react/pull/32538)
+ 104 more matches in this file
1---
2name: compiler-review
3▶description: Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
4model: opus
5color: green
· · ·
6---
7
8▶You are a React Compiler Rust port reviewer. Your job is to review Rust code in `compiler/crates/` for port fidelity, convention compliance, and correct error handling by comparing it against the original TypeScript source.
9
10## Input
· · ·
24| `react_compiler_lowering` | `src/HIR/BuildHIR.ts`, `src/HIR/HIRBuilder.ts` |
25| `react_compiler` | `src/Babel/`, `src/Entrypoint/` |
26▶| `react_compiler_diagnostics` | `src/CompilerError.ts` |
27| `react_compiler_<name>` | `src/<Name>/` (1:1, e.g., `react_compiler_optimization` -> `src/Optimization/`) |
28
· · ·
50- Naming: `snake_case` for functions/variables, `PascalCase` for types (matching Rust conventions)
51
52▶### Error Handling
53- Non-null assertions (`!` in TS) -> `.unwrap()` or similar panic
54- `CompilerError.invariant()`, `CompilerError.throwTodo()`, `throw` -> `Result<_, CompilerDiagnostic>` with `Err(...)`
· · ·
54▶- `CompilerError.invariant()`, `CompilerError.throwTodo()`, `throw` -> `Result<_, CompilerDiagnostic>` with `Err(...)`
55- `pushDiagnostic()` with invariant errors -> `return Err(...)`
56- `env.recordError()` or non-invariant `pushDiagnostic()` -> accumulate on `Environment` (keep as-is)
+ 3 more matches in this file
1---
2▶name: investigate-error
3description: Investigates React compiler errors to determine the root cause and identify potential mitigation(s). Use this agent when the user asks to 'investigate a bug', 'debug why this fixture errors', 'understand why the compiler is failing', 'find the root cause of a compiler issue', or when they provide a snippet of code and ask to debug. Use automatically when encountering a failing test case, in order to understand the root cause.
4model: opus
· · ·
3▶description: Investigates React compiler errors to determine the root cause and identify potential mitigation(s). Use this agent when the user asks to 'investigate a bug', 'debug why this fixture errors', 'understand why the compiler is failing', 'find the root cause of a compiler issue', or when they provide a snippet of code and ask to debug. Use automatically when encountering a failing test case, in order to understand the root cause.
4model: opus
5color: pink
· · ·
24- Proceed to binary search simplification
25
26▶### Step 3b: If the fixture errors
27Execute `yarn snap minimize --update <path-to-fixture>` to remove non-critical aspects of the failing test case. This **updates the fixture in place**.
28
· · ·
29▶Re-read the fixture file to see the latest, minimal reproduction of the error.
30
31### Step 4: Iteratively adjust the fixture until it stops erroring
· · ·
31▶### Step 4: Iteratively adjust the fixture until it stops erroring
32After the previous step the fixture will have all extraneous aspects removed. Try to make further edits to determine the specific feature that is causing the error.
33
+ 4 more matches in this file
48- **Two-phase collect/apply**: When you can't mutate through stored references, collect IDs first, then apply mutations
49- **Ordered maps**: Use `IndexMap`/`IndexSet` where TS uses `Map`/`Set` and iteration order matters
50▶- **Error handling**: Non-fatal errors accumulate on `env`; fatal errors return `Err`
51- **Structural similarity**: Target ~85-95% correspondence with TypeScript. A developer should be able to view TS and Rust side-by-side
52
· · ·
84- Missing match arms (Rust requires exhaustive matching)
85- Wrong iteration order (need `IndexMap` instead of `HashMap`)
86▶- Range off-by-one errors (mutable range start/end)
87- Formatting diffs (debug print format doesn't match TS)
88- Event mismatches (CompileError/CompileSkip events differ)
· · ·
88▶- Event mismatches (CompileError/CompileSkip events differ)
89- Missing handling for edge cases the TS handles implicitly
90- Identifier/scope lookups that should go through the arena
68| 49 | Codegen | ast | |
69
70▶Validation passes (no log entries, tested via CompileError/CompileSkip events):
71- After PruneMaybeThrows (#2): validateContextVariableLValues, validateUseMemo
72- After InferTypes (#9): validateHooksUsage, validateNoCapitalizedCalls (conditional)
· · ·
261Go back to Step 1. The loop continues until:
262- All passes are ported and clean (up to #49)
263▶- An unrecoverable error occurs
264
265## Key Principles
· · ·
266
267▶1. **Earliest failure wins**: Even a single test failure in pass #2 must be fixed before working on pass #11. Early errors cascade — a bug in lowering can cause false failures in every downstream pass.
268
2692. **Cumulative testing**: `test-rust-port.sh <PassName>` tests ALL passes up to and including the named pass. A clean result for the last pass implies all earlier passes are clean too.
30| `src/HIR/BuildHIR.ts`, `src/HIR/HIRBuilder.ts` | `react_compiler_lowering` |
31| `src/Babel/`, `src/Entrypoint/` | `react_compiler` |
32▶| `src/CompilerError.ts` | `react_compiler_diagnostics` |
33| `src/ReactiveScopes/` | `react_compiler_reactive_scopes` |
34| `src/<Name>/` | `react_compiler_<name>` (1:1, e.g., `src/Optimization/` -> `react_compiler_optimization`) |
1---
2name: compiler-review
3▶description: Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.
4---
5
· · ·
25 - Read the architecture guide
26 - Find and read the corresponding TypeScript files
27▶ - Review for port fidelity, convention compliance, and error handling
28 - Return a numbered issue list
29
8/**
9 * Our philosophy for linting is that lints should be very high-signal:
10▶ * - Error, don't warn. If it's worth mentioning it's worth fixing.
11 * - Enable rules that consistently identify real problems. If we frequently would have to
12 * disable the rule due to false positives, it isn't high-signal.
· · ·
42 "no-inner-declarations": "off",
43
44▶ "multiline-comment-style": ["error", "starred-block"],
45
46 /**
· · ·
53
54 /*
55▶ * Explicitly casting to/through any is sometimes required, often for error messages to
56 * assertExhaustive()
57 */
· · ·
66 // Being explicit provides value in cases where inference may later change
67 "@typescript-eslint/no-inferrable-types": "off",
68▶ "@typescript-eslint/explicit-function-return-type": "error",
69
70 /*
· · ·
74 */
75 "@typescript-eslint/no-unused-vars": [
76▶ "error",
77 {
78 argsIgnorePattern: "^_",
+ 2 more matches in this file
9## eslint-plugin-react-hooks
10* Temporarily disable ref access in render validation [#32839](https://github.com/facebook/react/pull/32839) by [@poteto](https://github.com/poteto)
11▶* Fix type error with recommended config [#32666](https://github.com/facebook/react/pull/32666) by [@niklasholm](https://github.com/niklasholm)
12* Merge rule from eslint-plugin-react-compiler into `react-hooks` plugin [#32416](https://github.com/facebook/react/pull/32416) by [@michaelfaith](https://github.com/michaelfaith)
13* Add dev dependencies for typescript migration [#32279](https://github.com/facebook/react/pull/32279) by [@michaelfaith](https://github.com/michaelfaith)
· · ·
28* Add shape for Array.from [#32522](https://github.com/facebook/react/pull/32522) by [@mofeiZ](https://github.com/mofeiZ)
29* Patch array and argument spread mutability [#32521](https://github.com/facebook/react/pull/32521) by [@mofeiZ](https://github.com/mofeiZ)
30▶* Make CompilerError compatible with reflection [#32539](https://github.com/facebook/react/pull/32539) by [@poteto](https://github.com/poteto)
31* Add simple walltime measurement [#32331](https://github.com/facebook/react/pull/32331) by [@poteto](https://github.com/poteto)
32* Improve error messages for unhandled terminal and instruction kinds [#32324](https://github.com/facebook/react/pull/32324) by [@inottn](https://github.com/inottn)
· · ·
32▶* Improve error messages for unhandled terminal and instruction kinds [#32324](https://github.com/facebook/react/pull/32324) by [@inottn](https://github.com/inottn)
33* Handle TSInstantiationExpression in lowerExpression [#32302](https://github.com/facebook/react/pull/32302) by [@inottn](https://github.com/inottn)
34* Fix invalid Array.map type [#32095](https://github.com/facebook/react/pull/32095) by [@mofeiZ](https://github.com/mofeiZ)