-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
graphql-cli doesn't create folders on Windows #277
Comments
How did you try it before if not bash? |
Following this doc, It seems to suggest you can use Windows. So I was just using Powershell. To clarify: when I said bash on windows, I meant Ubuntu on windows, i.e WSL. |
Same issue here when I use The same behavior when I use a standard command shell, Powershell or a MINGW64 Bash shell. End result:
Node: v9.8.0 |
Same issue on Windows 10 |
Works fine with adm-zip@0.4.7 |
This also fixes graphql-boilerplates/node-graphql-server#302 |
👍 v2.15.14 works fine now, but v2.16.0-beta.6 still seems to have the same issue? Just FYI. |
System:
Windows 10
Node v9.6.1
graphql-cli v2.15.9
I installed prisma, and created a new project with
prisma init projectname
.It went through the first two questions, e.g. database or full boilerplate, then asked what boilerplate. I selected node-advanced. It then downloaded the boilerplate and then installed all dependencies. However, there it stops. According to the docs, it should ask where to deploy it… so I then tried manually running
prisma deploy
and it throws a couple of errors, saying --\database\prisma.yml could not be found. as well as the prisma.yml. I opened the folder, and found it has installed the boilerplate like the below image.I then tried
graphql create projectname --boilerplate node-advanced
, as per this suggestion. However, the same thing happens. It seems to be appending the folder name to the filename, rather than creating a directory.I then tried this using bash on windows, and everything worked perfectly. So I am thinking it must be a windows issue?
The text was updated successfully, but these errors were encountered: