Santiago "Momo" Marín

Having the same issue here. Looks like a browser bug.

Well, it is a browser issue indeed. Browsers need an `access-control-expose-headers` header to make them avilable when using the `fetch` API while performing a CORS request ([more here](https://fetch.spec.whatwg.org/#http-access-control-expose-headers)). In short:...

@edamian You have to make sure the headers are returned by the server in the appropriate format. I've tested this solution extensively with a few apps and it works as...

Having the same issue here. Have you found a solution, @KhristenkoYura ?

I've finally given up and started using [vue-axios](https://github.com/imcvampire/vue-axios). It behaves the way you'd expect and is pretty much a drop-in replacement. This project has poor documentation and with things like...

@KhristenkoYura Yes, I was too, but having to do an extra request when you can refresh the token beforehand if needed is unnecessary and not optimal. Axios allows you to...

@hasezoey updated the log output :+1: I know the times are a reference but these particular lines: ```txt MongoMS:utils Mongo[46089] killProcess: given childProcess's PID was not alive anymore +35s MongoMS:utils...

I initially had the teardown on `afterAll` but it caused the tests to timeout. Then, I moved everything to global setup and teardown but had the same behavior, just that...

Just ran a test on a GitHub Actions runner and the behavior is the same: ```txt Test Suites: 3 passed, 3 total Tests: 3 passed, 3 total Snapshots: 0 total...

Of course: https://github.com/stgogm/mongoms-issue-676 Added you to the repo as well so you can check the actions logs.