keystonejs / create-keystone-app

CLI app that makes it easy to get started with Keystone
https://keystonejs.com/tutorials/getting-started-with-create-keystone-next-app
MIT License
40 stars 10 forks source link

Yarn and npm install fails #320

Closed emmarvpol closed 2 years ago

emmarvpol commented 2 years ago

Hello! Im trying to install keystone 6 with no luck. I didn't find anything relative to this issue.

yarn create keystone-app

This is a part of my terminal output.

yarn create v1.22.18
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...

success Installed "create-keystone-app@7.0.0" with binaries:
      - create-keystone-app
[#####################################################################] 262/262
✨ You're about to generate a project using Keystone 6 packages.

✔ What directory should create-keystone-app generate your app into? · api

⠸ Installing dependencies with yarn. This may take a few minutes.
⚠ Failed to install with yarn.
✖ Failed to install with npm.
Error: Command failed with exit code 1: npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/auto-id@0.16.0
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN   peer react@"^17.0.2 || ^18.0.0-0" from next@12.2.0
npm WARN   node_modules/next
npm WARN     next@"^12.1.5" from @keystone-6/core@2.1.0
npm WARN     node_modules/@keystone-6/core
npm WARN   39 more (react-clientside-effect, react-day-picker, react-dom, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^16.8.0 || 17.x" from @reach/auto-id@0.16.0
npm WARN node_modules/@reach/auto-id
npm WARN   @reach/auto-id@"0.16.0" from react-day-picker@8.0.7
npm WARN   node_modules/react-day-picker
npm WARN 
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN   peer react@"^16.8.0 || 17.x" from @reach/auto-id@0.16.0
npm WARN   node_modules/@reach/auto-id
npm WARN     @reach/auto-id@"0.16.0" from react-day-picker@8.0.7
npm WARN     node_modules/react-day-picker
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @reach/auto-id@0.16.0
npm WARN Found: react-dom@18.2.0
npm WARN node_modules/react-dom
npm WARN   peer react-dom@"^17.0.2 || ^18.0.0-0" from next@12.2.0
npm WARN   node_modules/next
npm WARN     next@"^12.1.5" from @keystone-6/core@2.1.0
npm WARN     node_modules/@keystone-6/core
npm WARN   9 more (react-popper, react-select, react-transition-group, ...)
node -v
v16.15.1

npm -v
8.12.1

yarn -v
1.22.18
mapsi-fixi commented 2 years ago

same error

lukaswozniak commented 2 years ago

same error

WenLonG12345 commented 2 years ago

same errors. Any solution?

dcousens commented 2 years ago

Hi @WenLonG12345,

We can't reproduce this problem, could you please paste the commands you used? Additionally, what node version (and operating system if possible) are you using?

emmarvpol commented 2 years ago

Im on Pop!_OS 22.04 LTS Command yarn create keystone-app

node -v
v16.15.1

npm -v
8.12.1

yarn -v
1.22.18
Achisingh commented 2 years ago

https://github.com/keystonejs/create-keystone-app/pull/317 aims to resolve the dependencies that were broken due to breaking changes in the latest keystone-6 release. The following changes were responsible for causing the first build to break in the postinstall as the generated schemas are different to what is initially provided:

mapsi-fixi commented 2 years ago

I resolved my issue. Error was taken in config because process.env.SESSION_SECRET is not setted. I have changed it in auth.ts by typing random string - it shoudl be in main config. Then i have run npm install

emmarvpol commented 2 years ago

I tried again and its seems to work for me now.

dcousens commented 2 years ago

Please re-open if this is a problem

ShaunXenonKhan commented 1 year ago

I am facing a similar problem, but I have found a workaround that works in my instance. Do I re-open this or create a new issue?

dcousens commented 1 year ago

@ShaunXenonKhan if you have resolved your problem, please post your resolution here for others benefit. However if you think it is something we need to resolve, please open a new issue.