Q:

Angular 7+ error: 'the property is not available on type Object'

I am using a service to make a simple HTTP get request to an API and the request is successful. I get back an object with properties and their values and when I subscribe and log the response all seem to work fine. If I then try to access a property on the response eg(console.log(response.title), I get an error that the property is not available on the object. What's strange to me is that the properties are defined as part of the response object. If I ignore the error, the program compiles and serves on Localhost and the same property giving an error is logged to the console. I even used the same property to output text in the DOM and it is rendered yet still the error shows and it does this on all properties of the response object. Is this a bug or am I missing something? I don't want to change the response because it's already an object which is exactly what I want.

A:

What's strange to me is that the properties are defined as part of the response object.

Doesn't matter. The error you're getting are TypeScript static errors. At the compile time, TypeScript has no idea of the shape of the response from API. You can tell it: where you have your http.get(//...args), specify: http.get</* type declaration here */>(//... args), even http.get<any>//... should solve the problem.
You can also do that during consumption: console.log((response as any).title), for example.
Here's a fork of your stackblitz:
https://stackblitz.com/edit/angular-ziheza?file=src%2Fapp%2Ftest.service.ts

