OSSForks/react
1
0
Fork 0
mirror of https://github.com/zebrajr/react.git synced 2026-01-15 12:15:22 +00:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity
Files
9b8060041b4dec3388c448f909e3d6387edefa69
react/scripts/error-codes/codes.json

376 lines
40 KiB
JSON
Raw Normal View History

Add a gulp script for extracting error codes (#6882)
2016-06-01 11:21:26 -07:00
{
"0": "React.addons.createFragment(...): Encountered an invalid child; DOM elements are not valid children of React components.",
"1": "update(): expected target of %s to be an array; got %s.",
"2": "update(): expected spec of %s to be an array; got %s. Did you forget to wrap your parameter in an array?",
"3": "update(): You provided a key path to update() that did not contain one of %s. Did you forget to include {%s: ...}?",
"4": "Cannot have more than one key in an object with %s",
"5": "update(): %s expects a spec of type 'object'; got %s",
"6": "update(): %s expects a target of type 'object'; got %s",
"7": "Expected %s target to be an array; got %s",
"8": "update(): expected spec of %s to be an array of arrays; got %s. Did you forget to wrap your parameters in an array?",
"9": "update(): expected spec of %s to be a function; got %s.",
"10": "findAllInRenderedTree(...): instance must be a composite component",
"11": "TestUtils.scryRenderedDOMComponentsWithClass expects a className as a second argument.",
"12": "ReactShallowRenderer render(): Invalid component element.%s",
"13": "ReactShallowRenderer render(): Shallow rendering works only with custom components, not primitives (%s). Instead of calling `.render(el)` and inspecting the rendered output, look at `el.props` directly instead.",
"14": "TestUtils.Simulate expects a component instance and not a ReactElement.TestUtils.Simulate will not work if you are using shallow rendering.",
"15": "reactComponentExpect(...): instance must be a composite component",
"16": "Do not override existing functions.",
"17": "All native instances should have a tag.",
"18": "Expected a component class, got %s.%s",
"19": "Expect a native root tag, instead got %s",
"20": "RawText \"%s\" must be wrapped in an explicit <Text> component.",
"21": "findNodeHandle(...): Argument is not a component (type: %s, keys: %s)",
"22": "findNodeHandle(...): Unable to find node handle for unmounted component.",
"23": "onlyChild must be passed a children with exactly one child.",
"24": "Mismatched list of contexts in callback queue",
"25": "Trying to release an instance into a pool of a different type.",
"26": "Unexpected node: %s",
"27": "Transaction.perform(...): Cannot initialize a transaction when there is already an outstanding transaction.",
"28": "Transaction.closeAll(): Cannot close transaction when none are open.",
"29": "accumulate(...): Accumulated items must be not be null or undefined.",
"30": "accumulateInto(...): Accumulated items must not be null or undefined.",
Avoid passing custom stacks to console.error (#18685) * Detect double stacks in the new format in tests * Remove unnecessary uses of getStackByFiberInDevAndProd These all execute in the right execution context already. * Set the debug fiber around the cases that don't have an execution context * Remove stack detection in our console log overrides We never pass custom stacks as part of the args anymore. * Bonus: Don't append getStackAddendum to invariants We print component stacks for every error anyway so this is just duplicate information.
2020-04-21 09:22:46 -07:00
"31": "Objects are not valid as a React child (found: %s). If you meant to render a collection of children, use an array instead.",
Add a gulp script for extracting error codes (#6882)
2016-06-01 11:21:26 -07:00
"32": "Unable to find element with ID %s.",
"33": "getNodeFromInstance: Invalid argument.",
"34": "React DOM tree root should always have a node reference.",
"35": "isAncestor: Invalid argument.",
"36": "getParentInstance: Invalid argument.",
"37": "_registerComponent(...): Target container is not a DOM element.",
"38": "parentComponent must be a valid React Component",
"39": "ReactDOM.render(): Invalid component element.%s",
"40": "unmountComponentAtNode(...): Target container is not a DOM element.",
"41": "mountComponentIntoNode(...): Target container is not valid.",
"42": "You're trying to render a component to the document using server rendering but the checksum was invalid. This usually means you rendered a different component type or props on the client from the one on the server, or your render() methods are impure. React cannot handle this case due to cross-browser quirks by rendering at the document root. You should look for environment dependent code in your components and ensure the props are the same client and server side:\n%s",
"43": "You're trying to render a component to the document but you didn't use server rendering. We can't do this without using server rendering due to cross-browser quirks. See ReactDOMServer.renderToString() for server rendering.",
"44": "findDOMNode was called on an unmounted component.",
"45": "Element appears to be neither ReactComponent nor DOMNode (keys: %s)",
"46": "renderToString(): You must pass a valid ReactElement.",
"47": "renderToStaticMarkup(): You must pass a valid ReactElement.",
"48": "injectDOMPropertyConfig(...): You're trying to inject DOM property '%s' which has already been injected. You may be accidentally injecting the same DOM property config twice, or you may be injecting two configs that have conflicting property names.",
"49": "DOMProperty: Properties that have side effects must use property: %s",
"50": "DOMProperty: Value can be one of boolean, overloaded boolean, or numeric value, but not a combination: %s",
"51": "dangerouslyRenderMarkup(...): Cannot render markup in a worker thread. Make sure `window` and `document` are available globally before requiring React when unit testing or use ReactDOMServer.renderToString for server rendering.",
"52": "dangerouslyRenderMarkup(...): Missing markup.",
"53": "Danger: Assigning to an already-occupied result index.",
"54": "Danger: Did not assign to every index of resultList.",
"55": "Danger: Expected markup to render %s nodes, but rendered %s.",
"56": "dangerouslyReplaceNodeWithMarkup(...): Cannot render markup in a worker thread. Make sure `window` and `document` are available globally before requiring React when unit testing or use ReactDOMServer.renderToString() for server rendering.",
"57": "dangerouslyReplaceNodeWithMarkup(...): Missing markup.",
"58": "dangerouslyReplaceNodeWithMarkup(...): Cannot replace markup of the <html> node. This is because browser quirks make this unreliable and/or slow. If you want to render to the root you must use server rendering. See ReactDOMServer.renderToString().",
Avoid passing custom stacks to console.error (#18685) * Detect double stacks in the new format in tests * Remove unnecessary uses of getStackByFiberInDevAndProd These all execute in the right execution context already. * Set the debug fiber around the cases that don't have an execution context * Remove stack detection in our console log overrides We never pass custom stacks as part of the args anymore. * Bonus: Don't append getStackAddendum to invariants We print component stacks for every error anyway so this is just duplicate information.
2020-04-21 09:22:46 -07:00
"59": "%s is a void element tag and must not have `children` or use `props.dangerouslySetInnerHTML`.",
Add a gulp script for extracting error codes (#6882)
2016-06-01 11:21:26 -07:00
"60": "Can only set one of `children` or `props.dangerouslySetInnerHTML`.",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"61": "`props.dangerouslySetInnerHTML` must be in the form `{__html: ...}`. Please visit https://reactjs.org/link/dangerously-set-inner-html for more information.",
Avoid passing custom stacks to console.error (#18685) * Detect double stacks in the new format in tests * Remove unnecessary uses of getStackByFiberInDevAndProd These all execute in the right execution context already. * Set the debug fiber around the cases that don't have an execution context * Remove stack detection in our console log overrides We never pass custom stacks as part of the args anymore. * Bonus: Don't append getStackAddendum to invariants We print component stacks for every error anyway so this is just duplicate information.
2020-04-21 09:22:46 -07:00
"62": "The `style` prop expects a mapping from style properties to values, not a string. For example, style={{marginRight: spacing + 'em'}} when using JSX.",
Add a gulp script for extracting error codes (#6882)
2016-06-01 11:21:26 -07:00
"63": "Must be mounted to trap events",
"64": "trapBubbledEvent(...): Requires node to be rendered.",
"65": "Invalid tag: %s",
"66": "<%s> tried to unmount. Because of cross-browser quirks it is impossible to unmount some top-level components (eg <html>, <head>, and <body>) reliably and efficiently. To fix this, have a single top-level component that never unmounts render these elements.",
"67": "Missing closing comment for text component %s",
"68": "Expected devtool events to fire for the child before its parent includes it in onSetChildren().",
"69": "Expected onSetDisplayName() to fire for the child before its parent includes it in onSetChildren().",
"70": "Expected onSetChildren() or onSetText() to fire for the child before its parent includes it in onSetChildren().",
"71": "Expected onMountComponent() to fire for the child before its parent includes it in onSetChildren().",
"72": "Expected onSetParent() and onSetChildren() to be consistent (%s has parents %s and %s).",
"73": "ReactClassInterface: You are attempting to override `%s` from your class specification. Ensure that your method names do not overlap with React methods.",
"74": "ReactClassInterface: You are attempting to define `%s` on your component more than once. This conflict may be due to a mixin.",
"75": "ReactClass: You're attempting to use a component class or function as a mixin. Instead, just use a regular object.",
"76": "ReactClass: You're attempting to use a component as a mixin. Instead, just use a regular object.",
"77": "ReactClass: Unexpected spec policy %s for key %s when mixing in component specs.",
"78": "ReactClass: You are attempting to define a reserved property, `%s`, that shouldn't be on the \"statics\" key. Define it as an instance property instead; it will still be accessible on the constructor.",
"79": "ReactClass: You are attempting to define `%s` on your component more than once. This conflict may be due to a mixin.",
"80": "mergeIntoWithNoDuplicateKeys(): Cannot merge non-objects.",
"81": "mergeIntoWithNoDuplicateKeys(): Tried to merge two objects with the same key: `%s`. This conflict may be due to a mixin; in particular, this may be caused by two getInitialState() or getDefaultProps() methods returning objects with clashing keys.",
"82": "%s.getInitialState(): must return an object or null",
"83": "createClass(...): Class specification must implement a `render` method.",
"84": "%s: %s type `%s` is invalid; it must be a function, usually from React.PropTypes.",
"85": "setState(...): takes an object of state variables to update or a function which returns an object of state variables.",
"86": "SimpleEventPlugin: Unhandled event type, `%s`.",
"87": "Cannot provide a checkedLink and a valueLink. If you want to use checkedLink, you probably don't want to use valueLink and vice versa.",
"88": "Cannot provide a valueLink and a value or onChange event. If you want to use value or onChange, you probably don't want to use valueLink.",
"89": "Cannot provide a checkedLink and a checked property or onChange event. If you want to use checked or onChange, you probably don't want to use checkedLink",
"90": "ReactDOMInput: Mixing React and non-React radio inputs with the same `name` is not supported.",
"91": "`dangerouslySetInnerHTML` does not make sense on <textarea>.",
"92": "If you supply `defaultValue` on a <textarea>, do not pass children.",
"93": "<textarea> can only have at most one child.",
"94": "Expected %s listener to be a function, instead got type %s",
"95": "processEventQueue(): Additional events were enqueued while processing an event queue. Support for this has not yet been implemented.",
"96": "EventPluginRegistry: Cannot inject event plugins that do not exist in the plugin ordering, `%s`.",
"97": "EventPluginRegistry: Event plugins must implement an `extractEvents` method, but `%s` does not.",
"98": "EventPluginRegistry: Failed to publish event `%s` for plugin `%s`.",
Refactor DOM plugin system to single module (#18025)
2020-02-14 08:10:42 +00:00
"99": "EventPluginRegistry: More than one plugin attempted to publish the same event name, `%s`.",
"100": "EventPluginRegistry: More than one plugin attempted to publish the same registration name, `%s`.",
Add a gulp script for extracting error codes (#6882)
2016-06-01 11:21:26 -07:00
"101": "EventPluginRegistry: Cannot inject event plugin ordering more than once. You are likely trying to load more than one copy of React.",
"102": "EventPluginRegistry: Cannot inject two different event plugins using the same name, `%s`.",
"103": "executeDirectDispatch(...): Invalid `event`.",
"104": "ReactCompositeComponent: injectEnvironment() can only be called once.",
"105": "%s(...): A valid React element (or null) must be returned. You may have returned undefined, an array or some other invalid object.",
"106": "%s.state: must be set to an object or null",
"107": "%s.getChildContext(): childContextTypes must be defined in order to use getChildContext().",
"108": "%s.getChildContext(): key \"%s\" is not defined in childContextTypes.",
"109": "%s.render(): A valid React element (or null) must be returned. You may have returned undefined, an array or some other invalid object.",
"110": "Stateless function components cannot have refs.",
"111": "There is no registered component for the tag %s",
"112": "getNextDescendantID(%s, %s): Received an invalid React DOM ID.",
"113": "getNextDescendantID(...): React has made an invalid assumption about the DOM hierarchy. Expected `%s` to be an ancestor of `%s`.",
"114": "getFirstCommonAncestorID(%s, %s): Expected a valid React DOM ID: %s",
"115": "traverseParentPath(...): Cannot traverse from and to the same ID, `%s`.",
"116": "traverseParentPath(%s, %s, ...): Cannot traverse from two IDs that do not have a parent path.",
"117": "traverseParentPath(%s, %s, ...): Detected an infinite loop while traversing the React DOM ID tree. This may be due to malformed IDs: %s",
"118": "updateTextContent called on non-empty component.",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"119": "addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's `render` method, or you have multiple copies of React loaded (details: https://reactjs.org/link/refs-must-have-owner).",
"120": "removeComponentAsRefFrom(...): Only a ReactOwner can have refs. You might be removing a ref to a component that was not created inside a component's `render` method, or you have multiple copies of React loaded (details: https://reactjs.org/link/refs-must-have-owner).",
Add a gulp script for extracting error codes (#6882)
2016-06-01 11:21:26 -07:00
"121": "performUpdateIfNecessary: Unexpected batch number (current %s, pending %s)",
"122": "%s(...): Expected the last optional `callback` argument to be a function. Instead received: %s.",
"123": "ReactUpdates: must inject a reconcile transaction class and batching strategy",
"124": "Expected flush transaction's stored dirty-components length (%s) to match dirty-components array length (%s).",
Revert "Revert "Missing a space for error 125"" (#8995)
2017-02-13 17:15:08 -06:00
"125": "ReactUpdates.asap: Can't enqueue an asap callback in a context where updates are not being batched.",
Add a gulp script for extracting error codes (#6882)
2016-06-01 11:21:26 -07:00
"126": "ReactUpdates: must provide a reconcile transaction class",
"127": "ReactUpdates: must provide a batching strategy",
"128": "ReactUpdates: must provide a batchedUpdates() function",
"129": "ReactUpdates: must provide an isBatchingUpdates boolean attribute",
"130": "Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: %s.%s",
"131": "Encountered invalid React node of type %s",
"132": "Ended a touch event which was not counted in trackedTouchCount.",
"133": "Touch object is missing identifier",
"134": "Touch data should have been recorded on start",
Fix error codes (#7999) * took codes.json from the 15-dev branch * fixed react:extract-errors task in gulpfile * generated error codes * Revert "generated error codes" This reverts commit b8f3aeed9d8f0d469edd5f6623fa6090930594d8. * Added a README for the error code system
2016-11-08 15:20:46 -05:00
"135": "Cannot find single active touch",
"136": "Attempted to update component `%s` that has already been unmounted (or failed to mount).",
Avoid passing custom stacks to console.error (#18685) * Detect double stacks in the new format in tests * Remove unnecessary uses of getStackByFiberInDevAndProd These all execute in the right execution context already. * Set the debug fiber around the cases that don't have an execution context * Remove stack detection in our console log overrides We never pass custom stacks as part of the args anymore. * Bonus: Don't append getStackAddendum to invariants We print component stacks for every error anyway so this is just duplicate information.
2020-04-21 09:22:46 -07:00
"137": "%s is a void element tag and must neither have `children` nor use `dangerouslySetInnerHTML`.",
Fix error codes (#7999) * took codes.json from the 15-dev branch * fixed react:extract-errors task in gulpfile * generated error codes * Revert "generated error codes" This reverts commit b8f3aeed9d8f0d469edd5f6623fa6090930594d8. * Added a README for the error code system
2016-11-08 15:20:46 -05:00
"138": "Touch object is missing identifier.",
"139": "ReactTestRenderer: .update() can't be called after unmount.",
"140": "Expected hook events to fire for the child before its parent includes it in onSetChildren().",
"141": "Expected onSetChildren() to fire for a container child before its parent includes it in onSetChildren().",
"142": "Expected onBeforeMountComponent() parent and onSetChildren() to be consistent (%s has parents %s and %s).",
Fix PropTypes production test so it works with error code system
2017-03-02 16:12:50 -08:00
"143": "React.Children.only expected to receive a single React element child.",
Updated error codes (after merging in missing code from 15 stable) (#10290)
2017-07-26 12:18:02 -07:00
"144": "Item must have been set",
"145": "hostContainerInfo should be populated before getPublicInstance is called.",
"146": "React Component in warnForMissingKey should have a _store. This error is likely caused by a bug in React. Please file an issue.",
"147": "Missing owner for string ref %s. This error is likely caused by a bug in React. Please file an issue.",
"148": "Expected ref to be a function or a string.",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"149": "Element ref was specified as a string (%s) but no owner was set. You may have multiple copies of React loaded. (details: https://reactjs.org/link/refs-must-have-owner).",
Updated error codes (after merging in missing code from 15 stable) (#10290)
2017-07-26 12:18:02 -07:00
"150": "An object is not an iterable. This error is likely caused by a bug in React. Please file an issue.",
"151": "An iterable object provided no iterator.",
"152": "%s(...): Nothing was returned from render. This usually means a return statement is missing. Or, to render nothing, return null.",
"153": "Resuming work not yet implemented.",
"154": "We should always have pending or current props. This error is likely caused by a bug in React. Please file an issue.",
"155": "An indeterminate component should never have mounted. This error is likely caused by a bug in React. Please file an issue.",
Include tag in begin/complete invariant (#16881)
2019-09-25 08:10:35 -07:00
"156": "Unknown unit of work tag (%s). This error is likely caused by a bug in React. Please file an issue.",
Updated error codes (after merging in missing code from 15 stable) (#10290)
2017-07-26 12:18:02 -07:00
"157": "Invalid type of work. This error is likely caused by a bug in React. Please file an issue.",
"158": "There must be pending props for an initial mount. This error is likely caused by a bug in React. Please file an issue.",
"159": "There should always be pending or memoized props. This error is likely caused by a bug in React. Please file an issue.",
"160": "Expected to find a host parent. This error is likely caused by a bug in React. Please file an issue.",
"161": "Invalid host parent fiber. This error is likely caused by a bug in React. Please file an issue.",
"162": "This should have a text node initialized. This error is likely caused by a bug in React. Please file an issue.",
"163": "This unit of work tag should not have side-effects. This error is likely caused by a bug in React. Please file an issue.",
"164": "A coroutine cannot have host component children.",
"165": "Should be resolved by now. This error is likely caused by a bug in React. Please file an issue.",
"166": "We must have new props for new mounts. This error is likely caused by a bug in React. Please file an issue.",
"167": "An indeterminate component should have become determinate before completing. This error is likely caused by a bug in React. Please file an issue.",
"168": "Unexpected context found on stack. This error is likely caused by a bug in React. Please file an issue.",
"169": "Expected to have an instance by this point. This error is likely caused by a bug in React. Please file an issue.",
"170": "Expected subtree parent to be a mounted class component. This error is likely caused by a bug in React. Please file an issue.",
"171": "Found unexpected detached subtree parent. This error is likely caused by a bug in React. Please file an issue.",
"172": "The custom dialog was already injected.",
"173": "Injected showDialog() must be a function.",
"174": "Expected host context to exist. This error is likely caused by a bug in React. Please file an issue.",
"175": "Expected prepareToHydrateHostInstance() to never be called. This error is likely caused by a bug in React. Please file an issue.",
"176": "Expected prepareToHydrateHostTextInstance() to never be called. This error is likely caused by a bug in React. Please file an issue.",
Invariant that throws when committing wrong tree (#15517) If React finishes rendering a tree, delays committing it (e.g. Suspense), then subsequently starts over or renders a new tree, the pending tree is no longer valid. That's because rendering a new work-in progress mutates the old one in place. The current structure of the work loop makes this hard to reason about because, although `renderRoot` and `commitRoot` are separate functions, they can't be interleaved. If they are interleaved by accident, it either results in inconsistent render output or invariant violations that are hard to debug. This commit adds an invariant that throws if the new tree is the same as the old one. This won't prevent all bugs of this class, but it should catch the most common kind. To implement the invariant, I store the finished tree on a field on the root. We already had a field for this, but it was only being used for the unstable `createBatch` feature. A more rigorous way to address this type of problem could be to unify `renderRoot` and `commitRoot` into a single function, so that it's harder to accidentally interleave the two phases. I plan to do something like this in a follow-up.
2019-05-13 16:15:50 -07:00
"177": "Cannot commit the same tree as before. This error is likely caused by a bug in React. Please file an issue.",
Updated error codes (after merging in missing code from 15 stable) (#10290)
2017-07-26 12:18:02 -07:00
"178": "Should have next effect. This error is likely caused by a bug in React. Please file an issue.",
"179": "Should have a pending commit. This error is likely caused by a bug in React. Please file an issue.",
"180": "Commit phase errors should be scheduled to recover with task priority. This error is likely caused by a bug in React. Please file an issue.",
Fix spelling errors and typos (#19138)
2020-06-15 19:59:44 -04:00
"181": "Switch statement should be exhaustive. This error is likely caused by a bug in React. Please file an issue.",
Updated error codes (after merging in missing code from 15 stable) (#10290)
2017-07-26 12:18:02 -07:00
"182": "performWork was called recursively. This error is likely caused by a bug in React. Please file an issue.",
"183": "Should have found an error boundary. This error is likely caused by a bug in React. Please file an issue.",
"184": "No error for given unit of work. This error is likely caused by a bug in React. Please file an issue.",
"185": "Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.",
"186": "Task updates can only be scheduled as a nested update or inside batchedUpdates.",
"187": "flushSync was called from inside a lifecycle method. It cannot be called when React is already rendering.",
"188": "Unable to find node on an unmounted component.",
"189": "Child was not found in either parent set. This indicates a bug in React related to the return pointer. Please file an issue.",
"190": "Return fibers should always be each others' alternates. This error is likely caused by a bug in React. Please file an issue.",
"191": "Invalid argument passed as callback. Expected a function. Instead received: %s",
"192": "React depends on requestAnimationFrame. Make sure that you load a polyfill in older browsers.",
"193": "The server renderer does not implement support for array children yet.",
"194": "Fiber needs to be injected to handle a fiber target for controlled events. This error is likely caused by a bug in React. Please file an issue.",
"195": "The internal instance must be a React host component. This error is likely caused by a bug in React. Please file an issue.",
"196": "Missing injection for fiber getContextForSubtree",
"197": "Injected invokeGuardedCallback() must be a function.",
Built 16.0.0 beta 3. Updated versions, results.json, and error codes
2017-08-03 16:05:28 -07:00
"198": "clearCaughtError was called but no error was captured. This error is likely caused by a bug in React. Please file an issue.",
"199": "Fiber owners should not show up in Stack stack traces.",
"200": "Target container is not a DOM element.",
"201": "ReactDOM.render(): Invalid component element. Instead of passing a string like 'div', pass React.createElement('div') or <div />.",
"202": "ReactDOM.render(): Invalid component element. Instead of passing a class like Foo, pass React.createElement(Foo) or <Foo />.",
"203": "ReactDOM.render(): Invalid component element. This may be caused by unintentionally loading two independent copies of React.",
"204": "ReactDOM.render(): Invalid component element.",
Fix for #10388. Renames renderToStream to renderToNodeStream. (#10425)
2017-08-10 12:23:00 -07:00
"205": "renderToNodeStream(): Invalid component element.",
"206": "renderToStaticNodeStream(): Invalid component element.",
"207": "ReactDOMServer.renderToNodeStream(): The streaming API is not available in the browser. Use ReactDOMServer.renderToString() instead.",
"208": "ReactDOMServer.renderToStaticNodeStream(): The streaming API is not available in the browser. Use ReactDOMServer.renderToStaticMarkup() instead.",
Built 16.0.0 beta 3. Updated versions, results.json, and error codes
2017-08-03 16:05:28 -07:00
"209": "renderToString(): Invalid component element.",
"210": "renderToStaticMarkup(): Invalid component element.",
"211": "Missing injection for fiber findDOMNode",
"212": "Missing injection for stack findDOMNode",
"213": "Element appears to be neither ReactComponent nor DOMNode. Keys: %s",
"214": "toTree() does not yet know how to handle nodes with tag=%s",
"215": "something went wrong",
"216": "Text children should already be flattened.",
"217": "ReactART does not support the type \"%s\"",
"218": "ReactART: Can not insert node before itself",
"219": "getInspectorDataForViewTag() is not available in production",
"220": "Container does not support insertBefore operation",
"221": "Tried to register two views with the same name %s",
16 beta 5 version bump and results JSON
2017-08-08 10:25:25 -07:00
"222": "View config not found for name %s",
"224": "Can't read from currently-mounting component. This error is likely caused by a bug in React. Please file an issue.",
"225": "Unexpected object passed to ReactTestInstance constructor (tag: %s). This is probably a bug in React.",
Update error codes and results.json (#10619) * Update results.json **what is the change?:** Ran the build after updating Yarn lockfile and recorded latest build size results. **why make this change?:** Let's get an idea of bundle size at this point, when we are preparing the 16.0 RC. **test plan:** NA **issue:** https://github.com/facebook/react/issues/8854 * Update error codes https://github.com/facebook/react/tree/master/scripts/release-manager#update-the-error-codes
2017-09-06 11:11:19 -07:00
"226": "Unsupported component type %s in test renderer. This is probably a bug in React.",
"227": "ReactDOM was loaded before React. Make sure you load the React package before loading ReactDOM.",
"228": "TestUtils.Simulate expected a DOM node as the first argument but received a React element. Pass the DOM node you wish to simulate the event on instead. Note that TestUtils.Simulate will not work if you are using shallow rendering.",
"229": "TestUtils.Simulate expected a DOM node as the first argument but received a component instance. Pass the DOM node you wish to simulate the event on instead.",
"230": "_processChildContext is not available in React 16+. This likely means you have multiple copies of React and are attempting to nest a React 15 tree inside a React 16 tree using unstable_renderSubtreeIntoContainer, which isn't supported. Try to make sure you have only one copy of React (and ideally, switch to ReactDOM.unstable_createPortal).",
Update error codes
2017-09-14 13:37:26 +01:00
"231": "Expected `%s` listener to be a function, instead got a value of `%s` type.",
"232": "_processChildContext is not available in React 16+. This likely means you have multiple copies of React and are attempting to nest a React 15 tree inside a React 16 tree using unstable_renderSubtreeIntoContainer, which isn't supported. Try to make sure you have only one copy of React (and ideally, switch to ReactDOM.createPortal).",
Update error codes
2017-09-26 08:44:21 -07:00
"233": "Unsupported top level event type \"%s\" dispatched",
[CS] Persistent Updates (#11260) * Update build size * [CS] Clone container instead of new root concept The extra "root" concept is kind of unnecessary. Instead of having a mutable container even in the persistent mode, I'll instead make the container be immutable too and be cloned. Then the "commit" just becomes swapping the previous container for the new one. * Change the signature or persistence again We may need to clone without any updates, e.g. when the children are changed. Passing in the previous node is not enough to recycle since it won't have the up-to-date props and children. It's really only useful to for allocation pooling. * Implement persistent updates This forks the update path for host fibers. For mutation mode we mark them as having an effect. For persistence mode, we clone the stateNode with new props/children. Next I'll do HostRoot and HostPortal. * Refine protocol into a complete and commit phase finalizeContainerChildren will get called at the complete phase. replaceContainer will get called at commit. Also, drop the keepChildren flag. We'll never keep children as we'll never update a container if none of the children has changed. * Implement persistent updates of roots and portals These are both "containers". Normally we rely on placement/deletion effects to deal with insertions into the containers. In the persistent mode we need to clone the container and append all the changed children to it. I needed somewhere to store these new containers before they're committed so I added another field. * Commit persistent work at the end by swapping out the container * Unify cloneOrRecycle Originally I tried to make the recyclable instance nullable but Flow didn't like that and it's kind of sketchy since the instance type might not be nullable. However, the real difference which one we call is depending on whether they are equal. We can just offload that to the renderer. Most of them won't need to know about this at all since they'll always clone or just create new. The ones that do know now have to be careful to compare them so they don't reuse an existing instance but that's probably fine to simplify the implementation and API. * Add persistent noop renderer for testing * Add basic persistent tree test * Test bail out This adds a test for bailouts. This revealed a subtle bug. We don't set the return pointer when stepping into newly created fibers because there can only be one. However, since I'm reusing this mechanism for persistent updates, I'll need to set the return pointer because a bailed out tree won't have the right return pointer. * Test persistent text nodes Found another bug. * Add persistent portal test This creates a bit of an unfortunate feature testing in the unmount branch. That's because we want to trigger nested host deletions in portals in the mutation mode. * Don't consider container when determining portal identity Basically, we can't use the container to determine if we should keep identity and update an existing portal instead of recreate it. Because for persistent containers, there is no permanent identity. This makes it kind of strange to even use portals in this mode. It's probably more ideal to have another concept that has permanent identity rather than trying to swap out containers. * Clear portals when the portal is deleted When a portal gets deleted we need to create a new empty container and replace the current one with the empty one. * Add renderer mode flags for dead code elimination * Simplify ReactNoop fix * Add new type to the host config for persistent configs We need container to stay as the persistent identity of the root atom. So that we can refer to portals over time. Instead, I'll introduce a new type just to temporarily hold the children of a container until they're ready to be committed into the permanent container. Essentially, this is just a fancy array that is not an array so that the host can choose data structure/allocation for it. * Implement new hooks Now containers are singletons and instead their children swap. That way portals can use the container as part of their identity again. * Update build size and error codes * Address comment * Move new files to new location
2017-10-18 18:28:23 -07:00
"234": "Event cannot be both direct and bubbling: %s",
"235": "Persistent reconciler is disabled.",
"236": "Noop reconciler is disabled.",
"237": "Mutating reconciler is disabled.",
"238": "Task updates can only be scheduled as a nested update or inside batchedUpdates. This error is likely caused by a bug in React. Please file an issue.",
"239": "Measure not implemented yet",
"240": "Text components are not supported for now.",
Update error codes for 16.1.0-beta release
2017-11-02 15:34:31 -07:00
"241": "Text components are not yet supported.",
"242": "%s: %s type `%s` is invalid; it must be a function, usually from the `prop-types` package, but received `%s`.",
"243": "renderRoot was called recursively. This error is likely caused by a bug in React. Please file an issue.",
"244": "Should have a previous and last root. This error is likely caused by a bug in React. Please file an issue.",
"245": "performWorkOnRoot was called recursively. This error is likely caused by a bug in React. Please file an issue.",
"246": "Should be working on a root. This error is likely caused by a bug in React. Please file an issue.",
Update error codes for 16.1.0-beta.1 release
2017-11-07 14:53:31 +00:00
"247": "A call cannot have host component children.",
"248": "Not implemented.",
Update error codes for 16.3.0-alpha.0 release
2018-02-02 13:01:33 -08:00
"249": "ReactShallowRenderer render(): Shallow rendering works only with custom components, but the provided element type was `%s`.",
"250": "batch.render: Cannot render a batch that already committed.",
"251": "batch.commit: Cannot commit a batch multiple times.",
"252": "The `document` global was defined when React was initialized, but is not defined anymore. This can happen in a test environment if a component schedules an update from an asynchronous callback, but the test has already finished running. To solve this, you can either unmount the component at the end of your test (and ensure that any asynchronous operations get canceled in `componentWillUnmount`), or you can change the test itself to be asynchronous.",
"253": "work.commit(): Cannot commit while already rendering. This likely means you attempted to commit from inside a lifecycle method.",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"254": "Element ref was specified as a string (%s) but no owner was set. This could happen for one of the following reasons:\n1. You may be adding a ref to a functional component\n2. You may be adding a ref to a component that was not created inside a component's render method\n3. You have multiple copies of React loaded\nSee https://reactjs.org/link/refs-must-have-owner for more information.",
Update error codes for 16.3.0-alpha.0 release
2018-02-02 13:01:33 -08:00
"255": "Expected ReactFbErrorUtils.invokeGuardedCallback to be a function.",
"257": "Portals are not currently supported by the server renderer. Render them conditionally so that they only appear on the client render.",
"258": "Unknown element-like object type: %s. This is likely a bug in React. Please file an issue.",
"259": "The experimental Call and Return types are not currently supported by the server renderer.",
Update error codes for 16.3.0-alpha.2 release
2018-03-14 13:26:40 -07:00
"260": "Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: %s.",
"261": "Cannot commit an incomplete root. This error is likely caused by a bug in React. Please file an issue.",
"262": "Expired work should have completed. This error is likely caused by a bug in React. Please file an issue.",
"263": "dispatch: Cannot dispatch during the render phase.",
"264": "An error logging effect should not have been scheduled if no errors were captured. This error is likely caused by a bug in React. Please file an issue.",
Fix double spaces. (#15641)
2019-05-28 11:34:18 -06:00
"265": "This unit of work tag cannot capture errors. This error is likely caused by a bug in React. Please file an issue.",
Update error codes for 16.3.2 release
2018-04-16 16:23:12 +01:00
"266": "A subscription must return an unsubscribe function.",
"267": "React.cloneElement(...): The argument must be a React element, but you passed %s.",
Record sizes
2018-05-13 21:12:25 +01:00
"268": "Argument appears to not be a ReactComponent. Keys: %s",
Update error codes for 16.4.0 release
2018-05-23 17:35:31 -07:00
"269": "Profiler must specify an \"id\" string and \"onRender\" function as props",
"270": "The current renderer does not support persistence. This error is likely caused by a bug in React. Please file an issue.",
"271": "Failed to replay rendering after an error. This is likely caused by a bug in React. Please file an issue with a reproducing case to help us find it.",
"273": "Nesting of <View> within <Text> is not currently supported.",
"274": "Text strings must be rendered within a <Text> component.",
Update error codes for 16.4.1 release
2018-06-13 17:20:35 +01:00
"275": "The current renderer does not support mutation. This error is likely caused by a bug in React. Please file an issue.",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"276": "React depends on requestAnimationFrame. Make sure that you load a polyfill in older browsers. https://reactjs.org/link/react-polyfills",
Update error codes for 16.5.0 release
2018-09-06 09:34:27 -07:00
"277": "Context.unstable_read(): Context can only be read while React is rendering, e.g. inside the render method or getDerivedStateFromProps.",
"278": "unstable_createRoot(...): Target container is not a DOM element.",
"279": "Trying to release an event instance into a pool of a different type.",
"280": "setRestoreImplementation() needs to be called to handle a target for controlled events. This error is likely caused by a bug in React. Please file an issue.",
"281": "Finished root should have a work-in-progress. This error is likely caused by a bug in React. Please file an issue.",
"282": "If the root does not have an updateQueue, we should have already bailed out. This error is likely caused by a bug in React. Please file an issue.",
"283": "Element type is invalid. Received a promise that resolves to: %s. Promise elements must resolve to a class or function.",
"284": "Expected ref to be a function, a string, an object returned by React.createRef(), or null.",
"285": "The root failed to unmount after an error. This is likely a bug in React. Please file an issue.",
Update error codes for 16.5.1 release
2018-09-13 19:11:31 +01:00
"286": "%s(...): the first argument must be a React class instance. Instead received: %s.",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"287": "It is not supported to run the profiling version of a renderer (for example, `react-dom/profiling`) without also replacing the `schedule/tracking` module with `schedule/tracking-profiling`. Your bundler might have a setting for aliasing both modules. Learn more at https://reactjs.org/link/profiling",
"288": "It is not supported to run the profiling version of a renderer (for example, `react-dom/profiling`) without also replacing the `schedule/tracing` module with `schedule/tracing-profiling`. Your bundler might have a setting for aliasing both modules. Learn more at https://reactjs.org/link/profiling",
Update error codes for 16.6.0-alpha.8af6728 release
2018-10-10 17:18:59 +01:00
"289": "Function components cannot have refs.",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"290": "Element ref was specified as a string (%s) but no owner was set. This could happen for one of the following reasons:\n1. You may be adding a ref to a function component\n2. You may be adding a ref to a component that was not created inside a component's render method\n3. You have multiple copies of React loaded\nSee https://reactjs.org/link/refs-must-have-owner for more information.",
Swap expect(ReactNoop) for expect(Scheduler) (#14971) * Swap expect(ReactNoop) for expect(Scheduler) In the previous commits, I upgraded our custom Jest matchers for the noop and test renderers to use Scheduler under the hood. Now that all these matchers are using Scheduler, we can drop support for passing ReactNoop and test roots and always pass Scheduler directly. * Externalize Scheduler in noop and test bundles I also noticed we don't need to regenerator runtime in noop anymore.
2019-02-28 12:54:47 -08:00
"291": "Log of yielded values is not empty. Call expect(Scheduler).toHaveYielded(...) first.",
"292": "The matcher `toHaveYielded` expects an instance of React Test Renderer.\n\nTry: expect(Scheduler).toHaveYielded(expectedYields)",
Update error codes for 16.6.0 release
2018-10-23 16:29:35 -07:00
"293": "Context can only be read while React is rendering, e.g. inside the render method or getDerivedStateFromProps.",
"294": "ReactDOMServer does not yet support Suspense.",
"295": "ReactDOMServer does not yet support lazy-loaded components.",
"296": "Log of yielded values is not empty. Call expect(ReactTestRenderer).unstable_toHaveYielded(...) first.",
Update error codes for 16.6.1 release
2018-11-06 18:28:50 -08:00
"297": "The matcher `unstable_toHaveYielded` expects an instance of React Test Renderer.\n\nTry: expect(ReactTestRenderer).unstable_toHaveYielded(expectedYields)",
"298": "Hooks can only be called inside the body of a function component.",
Set up experimental builds (#17071) * Don't bother including `unstable_` in error The method names don't get stripped out of the production bundles because they are passed as arguments to the error decoder. Let's just always use the unprefixed APIs in the messages. * Set up experimental builds The experimental builds are packaged exactly like builds in the stable release channel: same file structure, entry points, and npm package names. The goal is to match what will eventually be released in stable as closely as possible, but with additional features turned on. Versioning and Releasing ------------------------ The experimental builds will be published to the same registry and package names as the stable ones. However, they will be versioned using a separate scheme. Instead of semver versions, experimental releases will receive arbitrary version strings based on their content hashes. The motivation is to thwart attempts to use a version range to match against future experimental releases. The only way to install or depend on an experimental release is to refer to the specific version number. Building -------- I did not use the existing feature flag infra to configure the experimental builds. The reason is because feature flags are designed to configure a single package. They're not designed to generate multiple forks of the same package; for each set of feature flags, you must create a separate package configuration. Instead, I've added a new build dimension called the **release channel**. By default, builds use the **stable** channel. There's also an **experimental** release channel. We have the option to add more in the future. There are now two dimensions per artifact: build type (production, development, or profiling), and release channel (stable or experimental). These are separate dimensions because they are combinatorial: there are stable and experimental production builds, stable and experimental developmenet builds, and so on. You can add something to an experimental build by gating on `__EXPERIMENTAL__`, similar to how we use `__DEV__`. Anything inside these branches will be excluded from the stable builds. This gives us a low effort way to add experimental behavior in any package without setting up feature flags or configuring a new package.
2019-10-14 10:46:42 -07:00
"299": "createRoot(...): Target container is not a DOM element.",
Update error codes for 16.6.1 release
2018-11-06 18:28:50 -08:00
"300": "Rendered fewer hooks than expected. This may be caused by an accidental early return statement.",
Update error codes
2018-11-12 17:59:06 -08:00
"301": "Too many re-renders. React limits the number of renders to prevent an infinite loop.",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"302": "It is not supported to run the profiling version of a renderer (for example, `react-dom/profiling`) without also replacing the `scheduler/tracing` module with `scheduler/tracing-profiling`. Your bundler might have a setting for aliasing both modules. Learn more at https://reactjs.org/link/profiling",
Throw on unhandled SSR suspending (#16460) * Throw on unhandled SSR suspending * Add a nicer message when the flag is off * Tweak internal refinement error message
2019-08-19 19:53:02 +01:00
"303": "ReactDOMServer did not find an internal fallback frame for Suspense. This is a bug in React. Please file an issue.",
Update error codes
2018-11-12 17:59:06 -08:00
"304": "Maximum number of concurrent React renderers exceeded. This can happen if you are not properly destroying the Readable provided by React. Ensure that you call .destroy() on it if you no longer want to read from it, and did not read to the end. If you use .pipe() this should be automatic.",
React v16.7.0
2018-12-19 17:23:14 -08:00
"305": "The current renderer does not support hydration. This error is likely caused by a bug in React. Please file an issue.",
16.8.0
2019-02-06 08:04:00 +00:00
"306": "Element type is invalid. Received a promise that resolves to: %s. Lazy element type must resolve to a class or function.%s",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"307": "Hooks can only be called inside the body of a function component. (https://reactjs.org/link/invalid-hook-call)",
16.8.0
2019-02-06 08:04:00 +00:00
"308": "Context can only be read while React is rendering. In classes, you can read it in the render method or getDerivedStateFromProps. In function components, you can read it directly in the function body, but not inside Hooks like useReducer() or useMemo().",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"309": "Function components cannot have string refs. We recommend using useRef() instead. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-string-ref",
16.8.0
2019-02-06 08:04:00 +00:00
"310": "Rendered more hooks than during the previous render.",
"311": "Should have a queue. This is likely a bug in React. Please file an issue.",
Release 16.8.2
2019-02-14 19:12:42 +00:00
"312": "Rendered more hooks than during the previous render",
"313": "Unknown priority level. This error is likely caused by a bug in React. Please file an issue.",
"314": "Pinged unknown suspense boundary type. This is probably a bug in React.",
"315": "Suspense boundaries are never on the root. This is probably a bug in React.",
"316": "Expected skipPastDehydratedSuspenseInstance() to never be called. This error is likely caused by a bug in React. Please file an issue.",
"317": "Expected to have a hydrated suspense instance. This error is likely caused by a bug in React. Please file an issue.",
"318": "A dehydrated suspense component was completed without a hydrated node. This is probably a bug in React.",
"319": "A dehydrated suspense boundary must commit before trying to render. This is probably a bug in React.",
Release 16.8.5
2019-03-22 16:41:58 +00:00
"320": "Expected ReactFiberErrorDialog.showErrorDialog to be a function.",
refactor fb.me redirect link to reactjs.org/link (#19598) * refactor fb.me url to reactjs.org/link * Update ESLintRuleExhaustiveDeps-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js * Update createReactClassIntegration-test.js * Update ReactDOMServerIntegrationUntrustedURL-test.internal.js Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
2020-08-17 20:25:50 +08:00
"321": "Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:\n1. You might have mismatching versions of React and the renderer (such as React DOM)\n2. You might be breaking the Rules of Hooks\n3. You might have more than one copy of React in the same app\nSee https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.",
Lint rule for unminified errors (#15757) * Lint rule for unminified errors Add a lint rule that fails if an invariant message is not part of the error code map. The goal is to be more disciplined about adding and modifiying production error codes. Error codes should be consistent across releases even if their wording changes, for continuity in logs. Currently, error codes are added to the error code map via an automated script that runs right before release. The problem with this approach is that if someone modifies an error message in the source, but neglects to modify the corresponding message in the error code map, then the message will be assigned a new error code, instead of reusing the existing one. Because the error extraction script only runs before a release, people rarely modify the error code map in practice. By moving the extraction step to the PR stage, it forces the author to consider whether the message should be assigned a new error code. It also allows the reviewer to review the changes. The trade off is that it requires more effort and context to land new error messages, or to modify existing ones, particular for new contributors who are not familiar with our processes. Since we already expect users to lint their code, I would argue the additional burden is marginal. Even if they forget to run the lint command locally, they will get quick feedback from the CI lint job, which typically finishes within 2-3 minutes. * Add unreleased error messages to map
2019-05-29 11:29:04 -07:00
"322": "forwardRef requires a render function but was given %s.",
Avoid passing custom stacks to console.error (#18685) * Detect double stacks in the new format in tests * Remove unnecessary uses of getStackByFiberInDevAndProd These all execute in the right execution context already. * Set the debug fiber around the cases that don't have an execution context * Remove stack detection in our console log overrides We never pass custom stacks as part of the args anymore. * Bonus: Don't append getStackAddendum to invariants We print component stacks for every error anyway so this is just duplicate information.
2020-04-21 09:22:46 -07:00
"323": "React has blocked a javascript: URL as a security precaution.",
Lint rule for unminified errors (#15757) * Lint rule for unminified errors Add a lint rule that fails if an invariant message is not part of the error code map. The goal is to be more disciplined about adding and modifiying production error codes. Error codes should be consistent across releases even if their wording changes, for continuity in logs. Currently, error codes are added to the error code map via an automated script that runs right before release. The problem with this approach is that if someone modifies an error message in the source, but neglects to modify the corresponding message in the error code map, then the message will be assigned a new error code, instead of reusing the existing one. Because the error extraction script only runs before a release, people rarely modify the error code map in practice. By moving the extraction step to the PR stage, it forces the author to consider whether the message should be assigned a new error code. It also allows the reviewer to review the changes. The trade off is that it requires more effort and context to land new error messages, or to modify existing ones, particular for new contributors who are not familiar with our processes. Since we already expect users to lint their code, I would argue the additional burden is marginal. Even if they forget to run the lint command locally, they will get quick feedback from the CI lint job, which typically finishes within 2-3 minutes. * Add unreleased error messages to map
2019-05-29 11:29:04 -07:00
"326": "Expected a valid priority level",
"327": "Should not already be working.",
"328": "Should have a work-in-progress.",
"329": "Unknown root exit status.",
"330": "Should be working on an effect.",
"331": "Cannot flush passive effects while already rendering.",
"332": "Unknown priority level.",
"333": "This should have a parent host component initialized. This error is likely caused by a bug in React. Please file an issue.",
"334": "accumulate(...): Accumulated items must not be null or undefined.",
[Flare] Add useEvent hook implementation (#15927) * [Flare] Add useEvent hook implementation Validate hooks have decendent event components Few fixes and displayName changes Fix more responder bugs Update error codes * Add another test * Address feedback
2019-06-21 03:12:40 +01:00
"335": "ReactDOMServer does not yet support the event API.",
[Flare] Redesign core event system (#16163)
2019-07-23 23:46:44 +01:00
"338": "ReactDOMServer does not yet support the fundamental API.",
Refactor Partial Hydration (#16346) * Move dehydrated to be child of regular SuspenseComponent We now store the comment node on SuspenseState instead and that indicates that this SuspenseComponent is still dehydrated. We also store a child but that is only used to represent the DOM node for deletions and getNextHostSibling. * Move logic from DehydratedSuspenseComponent to SuspenseComponent Forked based on SuspenseState.dehydrated instead. * Retry logic for dehydrated boundary We can now simplify the logic for retrying dehydrated boundaries without hydrating. This is becomes simply a reconciliation against the dehydrated fragment which gets deleted, and the new children gets inserted. * Remove dehydrated from throw Instead we use the regular Suspense path. To save code, we attach retry listeners in the commit phase even though technically we don't have to. * Pop to nearest Suspense I think this is right...? * Popping hydration state should skip past the dehydrated instance * Split mount from update and special case suspended second pass The DidCapture flag isn't used consistently in the same way. We need further refactor for this. * Reorganize update path If we remove the dehydration status in the first pass and then do a second pass because we suspended, then we need to continue as if it didn't previously suspend. Since there is no fragment child etc. However, we must readd the deletion. * Schedule context work on the boundary and not the child * Warn for Suspense hydration in legacy mode It does a two pass render that client renders the content. * Rename DehydratedSuspenseComponent -> DehydratedFragment This now doesn't represent a suspense boundary itself. Its parent does. This Fiber represents the fragment around the dehydrated content. * Refactor returns Avoids the temporary mutable variables. I kept losing track of them. * Add a comment explaining the type. Placing it in the type since that's the central point as opposed to spread out.
2019-08-12 15:58:38 -07:00
"340": "Threw in newly mounted dehydrated component. This is likely a bug in React. Please file an issue.",
Throw on unhandled SSR suspending (#16460) * Throw on unhandled SSR suspending * Add a nicer message when the flag is off * Tweak internal refinement error message
2019-08-19 19:53:02 +01:00
"341": "We just came from a parent so we must have had a parent. This is a bug in React.",
[react-core] Add more support for experimental React Scope API (#16621)
2019-08-30 18:27:14 +01:00
"342": "A React component suspended while rendering, but no fallback UI was specified.\n\nAdd a <Suspense fallback=...> component higher in the tree to provide a loading indicator or placeholder to display.",
[Partial Hydration] Don't invoke listeners on parent of dehydrated event target (#16591) * Don't invoke listeners on parent of dehydrated event target * Move Suspense boundary check to getClosestInstanceFromNode Now getClosestInstanceFromNode can return either a host component, host text component or suspense component when the suspense component is dehydrated. We then use that to ignore events on a suspense component. * Attach the HostRoot fiber to the DOM container This lets us detect if an event happens on this root's subtree before it has rendered something. * Add todo The approach of checking isFiberMounted answers if we might be in an in-progress hydration but it doesn't answer which root or boundary might be in-progress so we don't know what to wait for. This needs some refactoring. * Refactor isFiberMountedImpl to getNearestMountedFiber We'll need the nearest boundary for event replaying so this prepares for that. This surfaced an issue that we attach Hydrating tag on the root but normally this (and Placement) is attached on the child. This surfaced an issue that this can lead to both Placement and Hydrating effects which is not supported so we need to ensure that we only ever use one or the other. * Add todo for bug I spotted * Cache tags * Check the ContainerInstanceKey before the InstanceKey The container is inside the instance, so we must find it before the instance, since otherwise we'll miss it.
2019-09-05 08:51:31 -07:00
"343": "ReactDOMServer does not yet support scope components.",
[suspense][error handling] Inline renderRoot and fix error handling bug (#16801) * Outline push/pop logic in `renderRoot` I want to get rid of the the `isSync` argument to `renderRoot`, and instead use separate functions for concurrent and synchronous render. As a first step, this extracts the push/pop logic that happens before and after the render phase into helper functions. * Extract `catch` block into helper function Similar to previous commit. Extract error handling logic into a separate function so it can be reused. * Fork `renderRoot` for sync and concurrent Removes `isSync` argument in favor of separate functions. * Extra "root completion" logic to separate function Moving this out to avoid an accidental early return, which would bypass the call to `ensureRootIsScheduled` and freeze the UI. * Inline `renderRoot` Inlines `renderRoot` into `performConcurrentWorkOnRoot` and `performSyncWorkOnRoot`. This lets me remove the `isSync` argument and also get rid of a redundant try-catch wrapper. * [suspense][error handling] Add failing unit test Covers an edge case where an error is thrown inside the complete phase of a component that is in the return path of a component that suspends. The second error should also be handled (i.e. able to be captured by an error boundary. The test is currently failing because there's a call to `completeUnitOfWork` inside the main render phase `catch` block. That call is not itself wrapped in try-catch, so anything that throws is treated as a fatal/unhandled error. I believe this bug is only observable if something in the host config throws; and, only in legacy mode, because in concurrent/batched mode, `completeUnitOfWork` on fiber that throws follows the "unwind" path only, not the "complete" path, and the "unwind" path does not call any host config methods. * [scheduler][profiler] Start time of delayed tasks Fixes a bug in the Scheduler profiler where the start time of a delayed tasks is always 0. * Remove ad hoc `throw` Fatal errors (errors that are not captured by an error boundary) are currently rethrown from directly inside the render phase's `catch` block. This is a refactor hazard because the code in this branch has to mirror the code that happens at the end of the function, when exiting the render phase in the normal case. This commit moves the throw to the end, using a new root exit status. * Handle errors that occur on unwind
2019-09-23 11:23:28 -07:00
"344": "Expected prepareToHydrateHostSuspenseInstance() to never be called. This error is likely caused by a bug in React. Please file an issue.",
[react-interactions] Remove context.setTimeout & context.clearTimeout (#17000)
2019-10-03 13:37:37 +02:00
"345": "Root did not complete. This is a bug in React.",
useMutableSource hook (#18000) useMutableSource hook useMutableSource() enables React components to safely and efficiently read from a mutable external source in Concurrent Mode. The API will detect mutations that occur during a render to avoid tearing and it will automatically schedule updates when the source is mutated. RFC: reactjs/rfcs#147
2020-03-11 12:34:39 -07:00
"348": "ensureListeningTo(): received a container that was not an element node. This is likely a bug in React.",
"349": "Expected a work-in-progress root. This is a bug in React. Please file an issue.",
[Flight] Integrate Blocks into Flight (#18371) * Resolve Server-side Blocks instead of Components React elements should no longer be used to extract arbitrary data but only for prerendering trees. Blocks are used to create asynchronous behavior. * Resolve Blocks in the Client * Tests * Bug fix relay JSON traversal It's supposed to pass the original object and not the new one. * Lint * Move Noop Module Test Helpers to top level entry points This module has shared state. It needs to be external from builds. This lets us test the built versions of the Noop renderer.
2020-03-23 17:53:45 -07:00
"350": "Cannot read from mutable source during the current render without tearing. This is a bug in React. Please file an issue.",
[Flight] Don't warn for key, but error for ref (#19986) * Improve error message by expanding the object in question * Don't warn for key/ref getters * Error if refs are passed in server components or to client components
2020-10-08 20:02:23 -04:00
"351": "Unsupported server component type: %s",
Remove Blocks (#20138) * Remove Blocks * Remove Flight Server Runtime There's no need for this now that the JSResource is part of the bundler protocol. Might need something for Webpack plugin specifically later. * Devtools
2020-10-31 02:03:45 -04:00
"352": "React Lazy Components are not yet supported on the server.",
Add getInspectorDataForViewAtPoint (take two) (#18388) * Add getInspectorDataForViewAtPoint (take two) * Updates from review * Add DEV to dev-only variable * Missed this rename
2020-03-30 15:42:41 -04:00
"353": "A server block should never encode any other slots. This is a bug in React.",
Add useOpaqueIdentifier Hook (#17322) * Add useOpaqueIdentifier Hook We currently use unique IDs in a lot of places. Examples are: * `<label for="ID">` * `aria-labelledby` This can cause some issues: 1. If we server side render and then hydrate, this could cause an hydration ID mismatch 2. If we server side render one part of the page and client side render another part of the page, the ID for one part could be different than the ID for another part even though they are supposed to be the same 3. If we conditionally render something with an ID , this might also cause an ID mismatch because the ID will be different on other parts of the page This PR creates a new hook `useUniqueId` that generates a different unique ID based on whether the hook was called on the server or client. If the hook is called during hydration, it generates an opaque object that will rerender the hook so that the IDs match. Co-authored-by: Andrew Clark <git@andrewclark.io>
2020-04-06 17:17:27 -07:00
"354": "getInspectorDataForViewAtPoint() is not available in production.",
[Blocks] Initial implementation of cache and data/fetch (#18774) * Rename ReactCache -> ReactCacheOld We still use it in some tests so I'm going to leave it for now. I'll start making the new one in parallel in the react package. * Add react/unstable-cache entry point * Add react-data entry point * Initial implementation of cache and data/fetch * Address review
2020-04-29 19:14:15 +01:00
"355": "The object passed back from useOpaqueIdentifier is meant to be passed through to attributes only. Do not read the value directly.",
Refine experimental Scopes API (#18778) * Refine experimental Scopes API
2020-05-01 19:01:43 +01:00
"356": "Could not read the cache.",
Initial Lanes implementation (#18796) See PR #18796 for more information. All of the changes I've made in this commit are behind the `enableNewReconciler` flag. Merging this to master will not affect the open source builds or the build that we ship to Facebook. The only build that is affected is the `ReactDOMForked` build, which is deployed to Facebook **behind an experimental flag (currently disabled for all users)**. We will use this flag to gradually roll out the new reconciler, and quickly roll it back if we find any problems. Because we have those protections in place, what I'm aiming for with this initial PR is the **smallest possible atomic change that lands cleanly and doesn't rely on too many hacks**. The goal has not been to get every single test or feature passing, and it definitely is not to implement all the features that we intend to build on top of the new model. When possible, I have chosen to preserve existing semantics and defer changes to follow-up steps. (Listed in the section below.) (I did not end up having to disable any tests, although if I had, that should not have necessarily been a merge blocker.) For example, even though one of the primary goals of this project is to improve our model for parallel Suspense transitions, in this initial implementation, I have chosen to keep the same core heuristics for sequencing and flushing that existed in the ExpirationTimes model: low priority updates cannot finish without also finishing high priority ones. Despite all these precautions, **because the scope of this refactor is inherently large, I do expect we will find regressions.** The flip side is that I also expect the new model to improve the stability of the codebase and make it easier to fix bugs when they arise.
2020-05-02 17:09:31 -07:00
"357": "The current renderer does not support React Scopes. This error is likely caused by a bug in React. Please file an issue.",
"358": "Invalid update priority: %s. This is a bug in React.",
Experimental test selector API (#18607) Adds several new experimental APIs to aid with automated testing. Each of the methods below accepts an array of "selectors" that identifies a path (or paths) through a React tree. There are four basic selector types: * Component: Matches Fibers with the specified React component type * Role: Matches Host Instances matching the (explicit or implicit) accessibility role. * Test name: Matches Host Instances with a data-testname attribute. * Text: Matches Host Instances that directly contain the specified text. * There is also a special lookahead selector type that enables further matching within a path (without actually including the path in the result). This selector type was inspired by the :has() CSS pseudo-class. It enables e.g. matching a <section> that contained a specific header text, then finding a like button within that <section>. API * findAllNodes(): Finds all Host Instances (e.g. HTMLElement) within a host subtree that match the specified selector criteria. * getFindAllNodesFailureDescription(): Returns an error string describing the matched and unmatched portions of the selector query. * findBoundingRects(): For all React components within a host subtree that match the specified selector criteria, return a set of bounding boxes that covers the bounds of the nearest (shallowed) Host Instances within those trees. * observeVisibleRects(): For all React components within a host subtree that match the specified selector criteria, observe if it’s bounding rect is visible in the viewport and is not occluded. * focusWithin(): For all React components within a host subtree that match the specified selector criteria, set focus within the first focusable Host Instance (as if you started before this component in the tree and moved focus forwards one step).
2020-05-05 10:37:46 -07:00
"360": "Invalid lane: %s. This is a bug in React.",
"361": "The current renderer does not support test selectors. This error is likely caused by a bug in React. Please file an issue.",
"362": "Could not find React container within specified host subtree.",
"363": "Test selector API is not supported by this renderer.",
"364": "Invalid host root specified. Should be either a React container or a node with a testname attribute.",
Add experimental ReactDOM.createEventHandle (#18756)
2020-05-12 20:24:25 +01:00
"365": "Invalid selector type %s specified.",
"366": "ReactDOM.createEventHandle: setListener called on an target that did not have a corresponding root. This is likely a bug in React.",
"367": "ReactDOM.createEventHandle: setListener called on an element target that is not managed by React. Ensure React rendered the DOM element.",
Refactor createEventHandle signature (#19174)
2020-07-07 13:05:06 +01:00
"368": "ReactDOM.createEventHandle: setListener called on an invalid target. Provide a valid EventTarget or an element managed by React.",
"369": "ReactDOM.createEventHandle: setter called on an invalid target. Provide a valid EventTarget or an element managed by React.",
Append text string to <Text> error message (#19581) * Append text string to <Text> error message * Truncate text in <Text> error message * Regenerate `codes.json`
2020-08-17 10:47:49 -07:00
"370": "ReactDOM.createEventHandle: setter called with an invalid callback. The callback must be a function.",
Attach Listeners Eagerly to Roots and Portal Containers (#19659) * Failing test for #19608 * Attach Listeners Eagerly to Roots and Portal Containers * Forbid createEventHandle with custom events We can't support this without adding more complexity. It's not clear that this is even desirable, as none of our existing use cases need custom events. This API primarily exists as a deprecation strategy for Flare, so I don't think it is important to expand its support beyond what Flare replacement code currently needs. We can later revisit it with a better understanding of the eager/lazy tradeoff but for now let's remove the inconsistency. * Reduce risk by changing condition only under the flag Co-authored-by: koba04 <koba0004@gmail.com>
2020-08-24 16:50:20 +01:00
"371": "Text string must be rendered within a <Text> component.\n\nText: %s",
[Flight] Support more element types and Hooks for Server and Hybrid Components (#19711) * Shim support for more element types * Shim commonly used Hooks that are safe * Flow * Oopsie
2020-08-27 20:19:13 +01:00
"372": "Cannot call unstable_createEventHandle with \"%s\", as it is not an event known to React.",
[Flight] Add Runtime Errors for Non-serializable Values (#19980) * Error on encoding non-serializable props * Add DEV time warnings to enforce that values are plain objects
2020-10-08 14:11:15 -04:00
"373": "This Hook is not supported in Server Components.",
"374": "Event handlers cannot be passed to client component props. Remove %s from these props if possible: %s\nIf you need interactivity, consider converting part of this to a client component.",
"375": "Functions cannot be passed directly to client components because they're not serializable. Remove %s (%s) from this object, or avoid the entire object: %s",
[Flight] Encode Symbols as special rows that can be referenced by models … (#20171) * Encode Symbols as special rows that can be referenced by models If a symbol was extracted from Symbol.for(...) then we can reliably recreate the same symbol on the client. S123:"react.suspense" M456:{mySymbol: '$123'} This doesn't suffer from the XSS problem because you have to write actual code to create one of these symbols. That problem is only a problem because values pass through common other usages of JSON which are not secure. Since React encodes its built-ins as symbols, we can now use them as long as its props are serializable. Like Suspense. * Refactor resolution to avoid memo hack Going through createElement isn't quite equivalent for ref and key in props. * Reuse symbol ids that have already been written earlier in the stream
2020-11-10 22:56:50 -05:00
"376": "Only global symbols received from Symbol.for(...) can be passed to client components. The symbol Symbol.for(%s) cannot be found among global symbols. Remove %s from this object, or avoid the entire object: %s",
[Flight] Add Runtime Errors for Non-serializable Values (#19980) * Error on encoding non-serializable props * Add DEV time warnings to enforce that values are plain objects
2020-10-08 14:11:15 -04:00
"377": "BigInt (%s) is not yet supported in client component props. Remove %s from this object or use a plain number instead: %s",
[Flight] Don't warn for key, but error for ref (#19986) * Improve error message by expanding the object in question * Don't warn for key/ref getters * Error if refs are passed in server components or to client components
2020-10-08 20:02:23 -04:00
"378": "Type %s is not supported in client component props. Remove %s from this object, or avoid the entire object: %s",
[Flight] Add getCacheForType() to the dispatcher (#20315) * Remove react/unstable_cache We're probably going to make it available via the dispatcher. Let's remove this for now. * Add readContext() to the dispatcher On the server, it will be per-request. On the client, there will be some way to shadow it. For now, I provide it on the server, and throw on the client. * Use readContext() from react-fetch This makes it work on the server (but not on the client until we implement it there.) Updated the test to use Server Components. Now it passes. * Fixture: Add fetch from a Server Component * readCache -> getCacheForType<T> * Add React.unstable_getCacheForType * Add a feature flag * Fix Flow * Add react-suspense-test-utils and port tests * Remove extra Map lookup * Unroll async/await because build system * Add some error coverage and retry * Add unstable_getCacheForType to Flight entry
2020-12-03 03:44:56 +00:00
"379": "Refs cannot be used in server components, nor passed to client components.",
"380": "Reading the cache is only supported while rendering.",
Error when the number of parameters to a query changes (#20379)
2020-12-04 20:11:00 +00:00
"381": "This feature is not supported by ReactSuspenseTestUtils.",
"382": "This query has received more parameters than the last time the same query was used. Always pass the exact number of parameters that the query needs.",
"383": "This query has received fewer parameters than the last time the same query was used. Always pass the exact number of parameters that the query needs."
Regenerate error codes and update bundle size stats (#10287)
2017-07-26 11:21:43 -07:00
}
Reference in New Issue Copy Permalink