Skip to content

'ng new project_name' always creates project in ~/ directory, regardless of where the command is run #1375

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
xingped opened this issue Jul 18, 2016 · 4 comments

Comments

@xingped
Copy link

xingped commented Jul 18, 2016

Please provide us with the following information:

  1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Mac OS X 10.11.5 (El Capitan)

  1. Versions. Please run ng --version. If there's nothing outputted, please
    run in a Terminal:
    node --version
    And paste the result here.

node: 6.2.0
angular-cli: 1.0.0-beta.9

  1. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.

run 'ng new project_name' in any directory and the project is always created in ~/

  1. The log given by the failure. Normally this include a stack trace and some
    more information.

No failure message other than the following:

(node:2520) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.

  1. Mention any other details that might be useful.

    Thanks! We'll be in touch soon.

@filipesilva
Copy link
Contributor

Dupe of #1079

@amazingandyyy
Copy link

amazingandyyy commented Aug 1, 2016

I have the same issue!!!!
how to fix this?

@filipesilva
Close this means what? in 1079 i didn't see a solution...

@filipesilva
Copy link
Contributor

@amazingandyyy see #1045 (comment)

@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 6, 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

3 participants