Even after ensuring the proper type checking, I am still receiving the error message "Property 'message' does not exist on type 'object'"

Question

Even after ensuring the proper type checking, I am still receiving the error message "Property 'message' does not exist on type 'object'"

I have the following code snippet:

try {
 // api call
} catch (error) {
  if (typeof error === 'object' && error !== null && 'message' in error) {
    if (typeof error.message === 'string') {
      if (error.message.match(userRejectedError)) {
        // do something
      } else {
        // do something else
      }
    }
  }
}

However, I am encountering the error:

Property 'message' does not exist on type 'object'

. Why is this happening when I have made sure to check all necessary types?

Edit: TSConfig

{
  "compilerOptions": {
    "baseUrl": ".",
    "target": "es6",
    "lib": ["dom", "dom.iterable", "esnext"],
    },
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "strictNullChecks": false,
    "noImplicitAny": false,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve"
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"],
  "exclude": ["node_modules"]
}

typescript

Answer 1

Answer №1

You're Not Ensuring Strict Type Checking

Currently, you are only verifying that the error instance is an object, not null, has a message property, and that the type of error.message is a string, instead of simply checking if the error instance is of type Error.

Utilize the instanceof keyword for type checking, rather than comparing with a string using typeof.

If you can guarantee that the error instance is of type Error, TypeScript can accurately infer that the instance will have the message property.

For example:

try{
/* some error-throwable code... */
} catch(error) {
  /* Use instanceof to compare types */
  if (error instanceof Error) {
    // Do something
  }
  /* Alternatively, you can use a switch statement */
  switch (error.constructor) {
    case Error:
      // Do something
  }
}

Refer to the link below for documentation on the Error type.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error

Answer 2

You're Not Ensuring Strict Type Checking

Currently, you are only verifying that the error instance is an object, not null, has a message property, and that the type of error.message is a string, instead of simply checking if the error instance is of type Error.

Utilize the instanceof keyword for type checking, rather than comparing with a string using typeof.

If you can guarantee that the error instance is of type Error, TypeScript can accurately infer that the instance will have the message property.

For example:

try{
/* some error-throwable code... */
} catch(error) {
  /* Use instanceof to compare types */
  if (error instanceof Error) {
    // Do something
  }
  /* Alternatively, you can use a switch statement */
  switch (error.constructor) {
    case Error:
      // Do something
  }
}

Refer to the link below for documentation on the Error type.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error

Even after ensuring the proper type checking, I am still receiving the error message "Property 'message' does not exist on type 'object'"

Answer №1

You're Not Ensuring Strict Type Checking

Similar questions

Hover shows no response

Determining the Type<> of a component based on a string in Angular 2

Is it possible to swap out the Firestore module `doc` with the `document` module

Is there a way to silence TypeScript's complaints about a React rendered value being converted into a Date object?

What is the best way to pass an array as a parameter in Angular?

How to Delete an Item from an Array in BehaviorSubject Using Angular/Typescript

Do changes in Input fields reflect in the parent component?

Having difficulty transferring data between components using @Input syntax

Stop modal from closing in the presence of an error

Unexpected Union Type Return from Apollo Server

Tips for eliminating a single occurrence with Array.prototype.filter()

Refresh Angular page data following new routing paths

How to troubleshoot Props not functioning in nextjs-typescript?

Utilizing a TypeScript function to trigger an action from within a Chart.js option callback

Angular 6: Sending Back HTTP Headers

Change the value of the checked property to modify the checked status

Encountered an error of 'No overload matches this call' while configuring ContextApi alongside useReducer with Typescript

Resolving TS2304 error using Webpack 2 and Angular 2

A conditional type used with an array to return either an Error object or a generic type when the array is destructured

Angular update row and save data to an array