meistrari / prompts-royale

Automatically create prompts and make them fight each other to know which is the best
https://promptsroyale.com
Other
546 stars 51 forks source link

Fresh clone, can't npm install #11

Closed atesgoral closed 1 year ago

atesgoral commented 1 year ago

Tried Node.js versions 20, 18, and 16 to see if it's a dependency compatibility issue, but the problem persists:

$ npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: prompts-royale@0.1.0
npm ERR! Found: vue@3.3.4
npm ERR! node_modules/vue
npm ERR!   vue@"^3.3.4" from nuxt@3.6.5
npm ERR!   node_modules/nuxt
npm ERR!     dev nuxt@"^3.6.2" from the root project
npm ERR!     peer nuxt@"^3.6.1" from @nuxt/devtools@0.7.0
npm ERR!     node_modules/@nuxt/devtools
npm ERR!       dev @nuxt/devtools@"latest" from the root project
npm ERR!     1 more (@vueuse/nuxt)
npm ERR!   peer vue@">=3.0.0" from @vueuse/motion@2.0.0
npm ERR!   node_modules/@vueuse/motion
npm ERR!     dev @vueuse/motion@"^2.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! vue-echarts@"^6.6.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: vue@2.6.14
npm ERR! node_modules/vue
npm ERR!   peer vue@">= 2.5 < 2.7" from @vue/composition-api@1.7.1
npm ERR!   node_modules/@vue/composition-api
npm ERR!     peerOptional @vue/composition-api@"^1.0.5" from vue-echarts@6.6.0
npm ERR!     node_modules/vue-echarts
npm ERR!       vue-echarts@"^6.6.0" 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.
npm ERR!
henrycunh commented 1 year ago

We use bun as the package manager!

Can you try installing it and then installing the dependencies through bun i? I will update the README to reflect this!

It's about 30x faster than npm https://bun.sh

atesgoral commented 1 year ago

Works fine with bun i!

atesgoral commented 1 year ago

Let's close when README is updated in case others run into the same issue.