Skip to content

Reusing App Name of Deleted App Not Allowed; "...already exists" #1133

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

Closed
edm00se opened this issue Jun 18, 2016 · 2 comments
Closed

Reusing App Name of Deleted App Not Allowed; "...already exists" #1133

edm00se opened this issue Jun 18, 2016 · 2 comments

Comments

@edm00se
Copy link

edm00se commented Jun 18, 2016

  1. OS?

Mac OSX El Capitan (10.11.5)

  1. Versions. Please run ng --version.
angular-cli: 1.0.0-beta.6
node: 4.4.5
os: darwin x64

npm is latest, at 3.9.6.

  1. Reproducible steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.
    • I had previously created a sample starter app name, e.g.- ng new some-app
    • delete the entire project folder (one level above the generated 'some-app' by angular-cli
    • create and change into a project folder (can be same or different name)
    • run ng new some-app again
    • observe output of command, an error, `Directory 'some-app' already exists.'; no files are created
  2. The log given by the failure. Normally this include a stack trace and some
    more information.

No log generated.

  1. Mention any other details that might be useful.

Is there some registry that is kept by angular-cli to keep track of app/project names on a system? I've tried uninstalling (globally, obviously) and reinstalling the angular-cli package to no avail.

@edm00se
Copy link
Author

edm00se commented Jun 18, 2016

This appears to be directly related to #1079 in that I apparently had a package.json in my user directory. My project directory was a subdirectory of my user dir. It also managed to install and persist some "missing" apps to that location. I sadly neglected to check the contents of the package.json, but to my knowledge it was not there beforehand.

I'm closing this as it appears to be covered by the above mentioned issue.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant