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

Can't install with new version of vuex-orm-next #12

Open
M3psipax opened this issue Apr 21, 2021 · 4 comments
Open

Can't install with new version of vuex-orm-next #12

M3psipax opened this issue Apr 21, 2021 · 4 comments

Comments

@M3psipax
Copy link

Describe the bug

cannot install this plugin because it depends on an older version

Steps to reproduce the bug

npm i @vuex-orm/plugin-axios-next

Expected behavior

installs

Versions

  • Vuex ORM Axios: 1.0.0-draft-2
  • Vuex ORM: 1.0.0-draft-10

Link to minimal reproduction

Additional context

Any chance this will get updated to work with newer versions?

@AaronGhent
Copy link

yarn add @vuex-orm/plugin-axios@next
and
npm i @vuex-orm/plugin-axios@next
seem to work :)

@melroy89
Copy link

Is there no 2021 version 1.0 final release yet?

@M3psipax
Copy link
Author

M3psipax commented Nov 5, 2021

yarn add @vuex-orm/plugin-axios@next and npm i @vuex-orm/plugin-axios@next seem to work :)

As you can see in

"@vuex-orm/core": "1.0.0-draft.4",
there's a dev dependency on "@vuex-orm/core": "1.0.0-draft.4".

Trying to install this with vuex-orm-next "@vuex-orm/core": "^1.0.0-draft.14" results in this error:

npm ERR! Found: @vuex-orm/[email protected]
npm ERR! node_modules/@vuex-orm/core
npm ERR!   @vuex-orm/core@"^1.0.0-draft.14" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @vuex-orm/core@"1.0.0-draft.4" from @vuex-orm/[email protected]
npm ERR! node_modules/@vuex-orm/plugin-axios
npm ERR!   @vuex-orm/plugin-axios@"1.0.0-draft.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

I'm not sure why npm thinks dev-dependencies should be relevant here, but that's apparently how it is.

I don't think it's an advisable approach to use the --force option, is it?

I don't understand why it works for you. Maybe an already installed older version of vuex-orm where you tried it?
I'm quite sure if you try this with a new project, you'll get the same error.

@michaelklopf
Copy link

@Danger89
Nothing is done in this project yet. The first draft you see here is just a shell.

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

4 participants