Javascript 未捕获的错误:不变违规:元素类型无效:应为字符串
声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow
原文地址: http://stackoverflow.com/questions/36501856/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Uncaught Error: Invariant Violation: Element type is invalid: expected a string
提问by James Nail
- i am trying to debug my react code.
- in my render method I try to put debugger and debugger.
- after I step over retun method its going to warning.js.
- after I step over warning.js if conditions its going to instantiateReactComponent.js
- I am not sure why its going to different files. can you tell me why its going to different files.
- not sure how to debug.
- it would be great if you guys give me some explaination so that in future I can fix the error my self
providing the snippet of the code where it goes in step over function call each time
error invariant.js?f23e:39 Uncaught Error: Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. Check the render method of
sports-container
.render() { const { sportsType, sportsDevice, sportsWordings, id } = this.props; let sportsEvent = true;
debugger; if (sportsEvent === true) { return (
warning.js
- 我正在尝试调试我的反应代码。
- 在我的渲染方法中,我尝试放置调试器和调试器。
- 在我跳过 retun 方法后,它会转到 warning.js。
- 在我跳过warning.js 之后,如果条件它会实例化ReactComponent.js
- 我不确定为什么它会转到不同的文件。你能告诉我为什么它会转到不同的文件。
- 不知道如何调试。
- 如果你们给我一些解释,以便将来我可以自己修复错误,那就太好了
提供代码片段,它每次都在函数调用中逐步执行
error invariant.js?f23e:39 Uncaught Error: Invariant Violation: 元素类型无效:需要一个字符串(对于内置组件)或一个类/函数(对于复合组件)但得到:未定义。检查 的渲染方法
sports-container
。渲染(){ const {sportsType,sportsDevice,sportsWordings,id } = this.props; 让sportsEvent = true;
debugger; if (sportsEvent === true) { return (
警告.js
/** * Similar to invariant but only logs a warning if the condition is not met. * This can be used to log issues in development environments in critical * paths. Removing the logging code for production environments will keep the * same logic and follow the same code paths. */
/** * 与 invariant 类似,但仅在不满足条件时记录警告。* 这可用于在关键路径中记录开发环境中的问题。删除生产环境的日志代码将保持*相同的逻辑并遵循相同的代码路径。*/
var warning = emptyFunction;
if (process.env.NODE_ENV !== 'production') {
warning = function (condition, format) {
for (var _len = arguments.length, args = Array(_len > 2 ? _len - 2 : 0), _key = 2; _key < _len; _key++) {
args[_key - 2] = arguments[_key];
}
if (format === undefined) {
throw new Error('`warning(condition, format, ...args)` requires a warning ' + 'message argument');
}
if (format.indexOf('Failed Composite propType: ') === 0) {
return; // Ignore CompositeComponent proptype check.
}
if (!condition) {
var argIndex = 0;
var message = 'Warning: ' + format.replace(/%s/g, function () {
return args[argIndex++];
});
if (typeof console !== 'undefined') {
console.error(message);
}
try {
// --- Welcome to debugging React ---
// This error was thrown as a convenience so that you can use this stack
// to find the callsite that caused this warning to fire.
throw new Error(message);
} catch (x) {}
}
};
}
instantiateReactComponent
instance.construct(node);
/** * Given a ReactNode, create an instance that will actually be mounted. * * @param {ReactNode} node * @return {object} A new instance of the element's constructor. * @protected */
/** * 给定一个 ReactNode,创建一个将实际挂载的实例。* * @param {ReactNode} 节点 * @return {object} 元素构造函数的新实例。* @保护*/
function instantiateReactComponent(node) {
var instance;
if (node === null || node === false) {
instance = new ReactEmptyComponent(instantiateReactComponent);
} else if (typeof node === 'object') {
var element = node;
!(element && (typeof element.type === 'function' || typeof element.type === 'string')) ? process.env.NODE_ENV !== 'production' ? invariant(false, 'Element type is invalid: expected a string (for built-in components) ' + 'or a class/function (for composite components) but got: %s.%s', element.type == null ? element.type : typeof element.type, getDeclarationErrorAddendum(element._owner)) : invariant(false) : undefined;
// Special case string values
if (typeof element.type === 'string') {
instance = ReactNativeComponent.createInternalComponent(element);
} else if (isInternalComponentType(element.type)) {
// This is temporarily available for custom components that are not string
// representations. I.e. ART. Once those are updated to use the string
// representation, we can drop this code path.
instance = new element.type(element);
} else {
instance = new ReactCompositeComponentWrapper();
}
} else if (typeof node === 'string' || typeof node === 'number') {
instance = ReactNativeComponent.createInstanceForText(node);
} else {
!false ? process.env.NODE_ENV !== 'production' ? invariant(false, 'Encountered invalid React node of type %s', typeof node) : invariant(false) : undefined;
}
if (process.env.NODE_ENV !== 'production') {
process.env.NODE_ENV !== 'production' ? warning(typeof instance.construct === 'function' && typeof instance.mountComponent === 'function' && typeof instance.receiveComponent === 'function' && typeof instance.unmountComponent === 'function', 'Only React Components can be mounted.') : undefined;
}
// Sets up the instance. This can probably just move into the constructor now.
instance.construct(node);
回答by James Nail
Check your import / require statements in your file, as well as the export for the components you're importing/requiring. When I get errors like this, it's usually because I'm either importing it incorrectly (ES6), i.e.
检查文件中的导入/要求语句,以及您导入/需要的组件的导出。当我遇到这样的错误时,通常是因为我错误地导入了它(ES6),即
import MyComponent from './my-component'
instead of
代替
import { MyComponent } from './my-component'
or maybe I've exported it incorrectly (forgetting to export default, or maybe exporting as default when I didn't mean to), or I forgot to export the component entirely.
或者我可能错误地导出了它(忘记导出默认值,或者可能在我无意中导出为默认值),或者我忘记完全导出组件。