Http utility in Server Side about react-pages

[catamphetamine]

Why do you think http is only available on client side?

[vetrslav]

I know that it's universal but as I understand this utility is available only in your middleware for async actions, and i want something like this in redux-thunk
I've tried to use getHttpClient() but it gave me an error that window is not defined on server side.

[catamphetamine]

I know that it's universal but as I understand this utility is avilable only in your middleware for async actions, and i want something like this in redux-thunk

I see.
Well, there is no global variable on server-side so getHttpClient() doesn't work there.
Instead, http client could be stored somewhere in store, like store.httpClient = httpClient but then how would one access store from an action... I guess it's not correct to access store from an action. In Redux, there's no way actually to access store directly, only getState(), but httpClient can't be stored in state because it's not a JSON object.

[catamphetamine]

I'll close this for now as "not possible".
Still you can write comments here.

[vetrslav]

ok, thanks
Yeah, that's it
I found something like workaround for this
workaround is to export some global variable (for example httpUtility) in source / redux / store.js
and to set
httpUtility = http_client
inside create_store function
it solves my needs
But i want it to be in npm package
Could you please add this in new version?
I think that this workaround is ok as i understand because we will use httpUtility always after the store is created
and it always gonna return correct http utility as on client and as on server

[catamphetamine]

I don't understand, which exact variable do you set inside create_store function.
You can post some actual code.

[vetrslav]

something like this in source / redux / store.js

[catamphetamine]

You can't share an httpClient between several users.
If you store it in a global variable then many users are using it simultaneously.
It's not supposed to be used like that: it should be constructed anew for each page for each user.

[vetrslav]

I get it, ok i will use common react-website approach for async actions.
thanks :)

[catamphetamine]

You should be able to do anything using the common react-website approach for async actions.
If there's a use-case where something is not possible then you can post it here.

[vetrslav]

ok, thanks