Type 'undefined' is not assignable to type 'RouterState' in strict mode. about typesafe-actions HOT 9 CLOSED

@zdila Thanks for reply. Good news - I managed to fix this without switching off strictNullCheck (with exact same package.json versions as you), by copying the react-router-redux typings into my own project and changing this line:

export const routerReducer: Reducer<RouterState>

to this

export const routerReducer: Reducer<RouterState, AnyAction>

See gist

I then instructed my project to always use these new typings here in the tsconfig.json:

Hope this helps you too!

from typesafe-actions.

Sorry but following the error message this issue clearly has nothing to do with this library.

from typesafe-actions.

Could you help me how to modyfy my code to not to need "strictFunctionTypes": false. I'll appreciate also if you forward me to better place for support. Thanks in advance.

from typesafe-actions.

It seems you have mismatched type definitions of react-router-redux and redux, you should investigate closely version you're using, I suspect you're using yarn which is very bugged in this regard and introduces a lot of duplicated packages, with JS you'll get away but with types there will be issues with compatibility of different versions

from typesafe-actions.

Thanks. I am using npm but I'll investigate according your suggestions.

from typesafe-actions.

So then please check if you are using redux@4 or even redux@4 types, this will clash because I think react-router-redux is still using redux@3

from typesafe-actions.

Relevant lines from our package.json:

"react": "16.3.2",
"react-dom": "16.3.2",
"react-redux": "5.0.7",
"react-router": "4.2.0",
"react-router-dom": "4.2.2",
"react-router-redux": "5.0.0-alpha.9",
"redux": "4.0.0",
"typesafe-actions": "2.0.0-1",
"@types/react": "16.3.14",
"@types/react-dom": "16.0.5",
"@types/react-redux": "6.0.0",
"@types/react-router-dom": "4.2.6",
"@types/react-router-redux": "5.0.14",

from typesafe-actions.

@zdila I'm having same issue - did you manage to resolve this? Thanks in advance.

from typesafe-actions.

@pdaddyo I am still using workaround mentioned in the issue description.

from typesafe-actions.