Closed thedevelopnik closed 3 years ago
I'm actually starting to wonder if this has less to do with this package and more with how this package runs in node instead of the browser, and if that promise catch has been silently failing and now the way this is running is catching it.
The effect is that the ssr server run from npm run ssr:serve
never responds. The request hangs in a pending state.
I'm trying to use this package on a frontend that calls to a separate api server backend. We use both http calls and websocket calls to our api server.
To authorize socket.io calls, we use passport.socketio.
When the server responds on some calls, the
set-cookie
header value is an array likeIn vue-resource.common.js, in the
nodeClient
this fails because it tries to call str.replace on all header values. The stack trace I'm getting isI'm having a hard time figuring out what in the ssr plugin is calling this. Happy to help with contributions if I can get help tracking down a fix. Thanks for any assistance!
Also happy to provide more info and clarification. It's late and I've been in this code for a few hours and the above may not be super clear.