roots new . deletes everything in current directory about roots HOT 6 CLOSED

I suppose, but really you'd have to be insane to type that and expect a good result. What's happening here, as you know, is that you are creating a new roots project called the name of the current folder. So it makes sense that it would overwrite the current folder with the new roots project. I can manually prevent the user from entering . or .. as the name, would that help?

from roots.

hmm we could just throw a warning @Jenius like are you sure bro?

from roots.

@Jenius Overwriting is fine, but not deleting everything in that folder, same goes for (roots new ./project). Root should only delete its own files. Here is user-case:

I was experimenting with deployd. Created new project with dpd init, then noticed I have empty public folder. Great let's try roots, roots new . puff. Everything gone (package.json,.git...) you get the point, how bad it is to delete everything. Also because command deletes folder and creates new, bash complained it lost pwd handle o.O.

from roots.

I also expect roots new app to write its files, overwriting them if they already exist, but not delete the whole directory. As @samccone said, it should at least warn the user.

from roots.

ok @dz0ny and @Kazy thanks for the feedback, this should fix it 💃

from roots.

closing it now that is has been merged

from roots.