The literal type of select(getPathname) doesn't relate to the value you get back from the yield. select(getPathname) is the value yielded by your co-routine to its iterating context.

The value injected into your generator by its running context (through the next() call) DOES matter to the type you get back from the yield expression.

Either way, currently Typescript has no metadata about what it's going to get at all, since your generator function has no type annotation.

I'm guessing this is redux-saga.

A typical Generator function type annotation is something like...

type WhatYouYield="foo"
type WhatYouReturn="bar"
type WhatYouAccept="baz"

function* myfun(): Generator<
  WhatYouYield,
  WhatYouReturn,
  WhatYouAccept
> {
const myYield = "foo" //type of myYield is WhatYouYield
const myAccepted = yield myYield; //type of myAccepted is WhatYouAccept
return "baz" //type of this value is WhatYouReturn 
}

...and the error you're getting is from Typescript having to guess the WhatYouAccept type without the Generator type annotation on your function.

I got same error and I solved it.

export interface ResponseGenerator{
    config?:any,
    data?:any,
    headers?:any,
    request?:any,
    status?:number,
    statusText?:string
}

const response:ResponseGenerator = yield YOUR_YIELD_FUNCTION
console.log(response.data)

In recent updates of typescript, there are more type restrictions on generator functions.

Type 1: yield with call

function* initDashboard(): any {
  let response = yield call(getDashboardData);
  console.log(response);
}

Type 2: yield without call

function* initDashboard() {
  let response: any = yield getDashboardData;
  console.log(response);
}

Note: Using any is fastest solution but proper solution would be creating type/interface for the response and using it as type.