Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Ky breaks Vuex #38

Closed
RobsonMi opened this issue Jan 28, 2022 · 2 comments
Closed

Using Ky breaks Vuex #38

RobsonMi opened this issue Jan 28, 2022 · 2 comments

Comments

@RobsonMi
Copy link

I am writing an app for web and electron using Quasar. I wanted to move from axios to Ky but as soon as I replace it Vuex store refuses to accept changes to it's state. store.commit works and I am able to log payload data and current store values but no mutations are accepted by store without any errors or warnings. This is very interesting and I can't pin where it fails. Any help would be appreciated.

@darrinmn9
Copy link

I have a large app with Vue/Vuex + Ky and it works just fine. It is most likely something specific to your app.

Also, how can you expect someone to help you without any repro steps, error messages, code, dependency versions, etc?

@sholladay
Copy link
Collaborator

sholladay commented Feb 23, 2022

Closing for lack of info. As Darrin said, at the very least we would need some reproduction steps or other specific details to move forward in helping you.

That said, my best guess given your description is that you reinstalled your dependencies while migrating to Ky. In doing so, you probably also (perhaps unknowingly) updated Vuex or other dependencies. This can happen even if you have pinned dependency versions in your package.json, when you run npm install by itself (without a specific package name).

If you can provide something reproducible, I'd be happy to re-open this issue and look into it further. Otherwise, try going back to Axios to see if it still works and double check that all of your dependencies (including sub-dependencies) are exactly the same. If that doesn't help, I suggest posting this on StackOverflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants