set_user | PostgreSQL extension allowing privilege escalation

To me it looks like a typo, handleGetUsers vs handleGetUser :)

Never pass the user id as plaintext through the parameters. Get it from the session instead. Its trivial for any malicous user to use the web inspector and simply fill in the hidden input and then upload a unseemly picture as ANY user.

The session cookie is encrypted and much more difficult to tamper with.

Getters are meant to compute derived state based on store state.

You are facing this problem because you are returning the value of localStorage.getItem() from your Getter, which is not a value of the store state, thus it is not reactive nor observable.

In your example, Vuex will not recompute the value of the Getter when you call localStorage.setItem().
It will recompute the Getter's value only when state.user.token is changed.

So, if you want to have the Getter working correctly, return just the value of state.user.token.
You can also add a created hook in your App.vue that would check if there is a token in the localStorage and call the SET_TOKEN mutation, if that is what you were trying to accomplish by calling localStorage.getItem in your Getter:

Your RestTuple conditional type is preventing the compiler from contextually inferring the callback parameter, as it would require inference to work "backwards" through the definition of RestTuple.

Instead, I'd be inclined to make your function generic only in that tuple type T, like this:

LoginUseReducer needs to be rendered like a component and not called like a function

since you're using typescript with react, I believe you have added the getSpotifyUser function to your interface, now if you want to access that i think you should call it like this

props.getSpotifyUser(access_token)

and finally add it to your connect as a dispatch function that's wrapping your component

your login component should be like this one

I can't reproduce your exact problem but I think your PrivateRoute is wrong. Try something like the example bellow.

The error occurs because currentUser is undefined when this blocks is executed, so you need to wait for auth been updated.

Add auth as dependency in useEffect:

Your login() function NEVER rejects the promise it returns so therefore await login() will never go to the catch. The login() function sometimes does return err, but that's just a value being returned, not a rejected promise. If you want the promise that login() returns to be rejected, then you must throw err instead of return err in login() from within your catch() block.