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

CLI gives an error when creating project with nuxt as the frontend #184

Open
3 tasks done
pedroalves80 opened this issue Nov 27, 2024 · 2 comments
Open
3 tasks done
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@pedroalves80
Copy link

Required check list:

  • I didn't find in the repository's issues section a similar bug.
  • I understand, this is an Open Source and not-for-profit product.
  • This is not about a third-party project, framework, or technology.

My environment:

  • OS (MINGW64_NT-10.0-26100 A1026504 3.3.6-bec3d608-341.x86_64 2023-02-22 08:29 UTC x86_64 Msys):
  • Go (go version go1.23.2 windows/amd64):

Describe the bug:
When creating a go project with nuxt as the frontend, the cli gives an error saying '[ERROR]exit status 1'.

Steps to reproduce the behavior:

  1. cgapp create
  2. select nuxt as frontend

Expected behavior:
Should not give any error, and create the root files, same as the other frontend technologies.

Screenshots:
image

@pedroalves80 pedroalves80 added bug Something isn't working help wanted Extra attention is needed labels Nov 27, 2024
Copy link

welcome bot commented Nov 27, 2024

Hey! 👋 Thanks for opening your first issue here! Be sure to follow the issue template.

@yunhailuo
Copy link

I hit the same error and Googled my way here. I'm not sure but I noticed if I run nuxi independently, it always asks for package manager and whether to init git. I see no other way to run it non-interactively yet. If I'm not answering those two questions and ctrl-C, I got the same amount limited content in results as cgapp without package installed etc. So I'm thinking this might be the reason.

If so, specifying --git-init false and --package-manager npm might be the way to go. Not knowing if this is the right fix, I did a quick dirty test and it worked with [INFO] Completed in 30 seconds! for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants