React Error Property 'X' does not exist on type 'Readonly<{}>'
The React.js error “Property does not exist on type 'Readonly<{}>'” occurs when we try to access the props or state of an untyped class component. To fix the error, you need to use generics on the React.Component class to type the props or state object of that class.
Below is an example of where the error occurs.
import React from 'react';
class App extends React.Component {
constructor(props: any) {
super(props);
this.state = {value: ''}; // Using state, but we didn't enter it
}
handleChange = (event: any) => {
this.setState({value: event.target.value});
};
render() {
return (
<div>
<form>
{/*
⛔️ Error:
Property 'value' does not exist on type 'Readonly<{}>'.ts(2339)
*/}
<input
onChange={this.handleChange}
type="text"
value={this.state.value}
/>
<button type="submit">Submit</button>
</form>
</div>
);
}
}
export default App;
Notice that our class component has a value property in its state object.
The reason for the error is – we have not entered the state object of the class, so if we try to access any property of the state object, we will get an error.
The same is true for the props object - if we don't explicitly type it, trying to access a property on the props object will result in an error.
To resolve this error, you need to use React.Component
generics for the class React.Component<PropsObject, StateObject>
.
import React from 'react';
// We set props to an empty object and state to {value: string}
class App extends React.Component<{}, {value: string}> {
constructor(props: any) {
super(props);
this.state = {value: ''};
}
handleChange = (event: any) => {
this.setState({value: event.target.value});
};
render() {
return (
<div>
<form>
<input
onChange={this.handleChange}
type="text"
// ✅ Everything is working fine now
value={this.state.value}
/>
<button type="submit">Submit</button>
</form>
</div>
);
}
}
export default App;
We typed the value property on the state object in our class, so we can now access it as this.state.value .
We pass an empty object for the type of the props object since this class doesn't accept any props.
If we don't know how the props or state objects will be typed and want to disable type checking, use the any type.
import React from 'react';
// 👇️ Disable type checking for props and state
class App extends React.Component<any, any> {
constructor(props: any) {
super(props);
this.state = {value: ''};
}
handleChange = (event: any) => {
this.setState({value: event.target.value});
};
render() {
return (
<div>
<form>
<input
onChange={this.handleChange}
type="text"
value={this.state.value}
/>
<button type="submit">Submit</button>
</form>
</div>
);
}
}
export default App;
We used the any type when typing the props and state objects, which effectively turned off type checking.
Now we can access any property on the this.props and this.state objects without getting type checking errors.
Here is an example of a class that also explicitly types the props object.
import React from 'react';
// 👇️ type props as {name: string}, and state as {value: string}
class App extends React.Component<{name: string}, {value: string}> {
constructor(props: any) {
super(props);
this.state = {value: ''};
}
handleChange = (event: any) => {
this.setState({value: event.target.value});
};
render() {
return (
<div>
<form>
<input
onChange={this.handleChange}
type="text"
value={this.state.value}
/>
<button type="submit">Submit</button>
</form>
<h1>{this.props.name}</h1>
</div>
);
}
}
export default App;
We explicitly typed the props object of the App component to have a name property of type string. Now, when we use the component, we must provide a name property, for example <App name="James Doe" />
.
To resolve the React.js error "Property does not exist on type 'Readonly<{}>'", make sure to explicitly type the class's props or state object, adding any properties we intend to access on the props or state object
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
How to avoid cross-origin (CORS) issues in React/Next.js
Publish Date:2025/03/17 Views:170 Category:NETWORK
-
In this article, we will introduce how to avoid cross-origin (CORS) issues in React/Next.js. Cross-origin resource sharing (CORS) is a protocol that defines how web requests should be handled when crossing different URLs.
React Tutorial - Transferring Props
Publish Date:2025/03/16 Views:188 Category:React
-
React transfers Props. Props are generated when components are encapsulated. Components expose some properties (Props) to the outside world to complete some functions.
React Tutorial: Props Anti-Pattern
Publish Date:2025/03/16 Views:187 Category:React
-
React's Props anti-pattern, using Props to generate state in getInitialState is an anti-pattern - Anti-Pattern.
React Tutorial - Props Validation
Publish Date:2025/03/16 Views:102 Category:React
-
Props validation is a very useful way to use components correctly. It can avoid many bugs and problems as your application becomes more and more complex. In addition, it can make your program more readable.
React tutorial: Types of Props for child components
Publish Date:2025/03/16 Views:172 Category:React
-
Usually, the child components of a React component are a group, that is, the child components are an array. Introduction to Type of the Children Props.
How to solve the error Uncaught TypeError: Cannot read properties of undefined in
Publish Date:2025/03/16 Views:153 Category:React
-
In the process of React development, we often encounter some errors. Here we look at an error reported in App.js. The error is as follows: App.js:69 Uncaught TypeError: Cannot read properties of undefined (reading 'setState') at onInput
Why do you need to bind event handlers in React Class Components?
Publish Date:2025/03/16 Views:60 Category:React
-
When using React, we must have come across control components and event handlers. We need to use `.bind()` in the constructor of the custom component to bind these methods to the component instance. As shown in the following code:
Solution to the error "does not contain a default export" in React
Publish Date:2025/03/16 Views:191 Category:React
-
When we try to use `default import` to import from a module that does not have a `default export`, we get a "does not contain a default export" error. To fix the error, make sure the module has named exports and wrap the import in curly braces, e.g.
Error in React: Attempted import error 'X' is not exported from Solution
Publish Date:2025/03/16 Views:78 Category:React
-
In React, the error “Attempted import error 'X' is not exported from” in React.js occurs when we try to import a named import that does not exist in the specified file. To fix the error, make sure the module has named exports and you have not obfu