You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 4, 2025. It is now read-only.
It would be really handy if the .git directory is ignored when [out-dir] is checked for existing contents. Adding --overwrite-dir in v3.7.0 was a step in the right direction, but I (and I believe many others) would still prefer the safety of not using a forceful operation when running the cli in a cloned empty repository (with a .git directory).
A common workflow for many is:
Clone empty repository.
Run create-nuxt-app without providing an outDir.
Get an error because the directory technically isn't empty (.git).
Re-run create-nuxt-app providing an outDir.
Immediately copy all of the generated files out of the outDir into the root of the repository.
Delete the leftover outDir.
This is obviously a fairly opinionated issue, but I'd love to hear some counter arguments.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
(Semi-related to #582, but not a duplicate)
It would be really handy if the
.git
directory is ignored when[out-dir]
is checked for existing contents. Adding --overwrite-dir in v3.7.0 was a step in the right direction, but I (and I believe many others) would still prefer the safety of not using a forceful operation when running the cli in a cloned empty repository (with a.git
directory).A common workflow for many is:
.git
).This is obviously a fairly opinionated issue, but I'd love to hear some counter arguments.
The text was updated successfully, but these errors were encountered: