-dir flag not being respected #5867

Activity

1. berwyn

   changed the title [-]`--dir` flag not being respected[/-] [+]`-dir` flag not being respected[/+] on Apr 6, 2017
2. delasteve commented on Apr 27, 2017

   

   delasteve

   on Apr 27, 2017

   Contributor

   More actions

   I was unable to reproduce this using

   @angular/cli: 1.0.1
   node: 7.9.0
   os: win32 x64
   

   Using ng new -dir foo someapp, when I lsed the parent directory, I got

   Mode                LastWriteTime         Length Name
   ----                -------------         ------ ----
   d-----        4/27/2017  11:58 AM                foo
   
3. berwyn commented on Apr 27, 2017

   

   berwyn

   on Apr 27, 2017

   Last edited by berwyn

   Author

   More actions

   My apologies, I debugged it more and found that the issue required more specific conditions to dupe and forgot to update this bug report. This is specifically if a directory above contains a package.json file. In my case, I was building a group of modules with lerna, where one was an Angular app. Angular CLI 1.0.0 would create the app at the top-level next to package.json rather than in the directory specified by -dir. I have not attempted with 1.0.1 yet, so this may be fixed (I'll report back when I have a chance to test)

   In other words, my expected setup was

   ng new -dir packages/foo-app foo

   resulting in

   ./
   |- package.json # Top level
   |- lerna.json
   `- packages
      `- foo-app
        |- .angular-cli.json
        |- karma.conf.js
        ...
   

   but instead I got

   ./
   |- package.json
   |- lerna.json
   |- .angular-cli.json
   |- karma.conf.js
   ...
   
4. filipesilva commented on May 4, 2017

   

   filipesilva

   on May 4, 2017

   Contributor

   More actions

   I actually thought we fixed this already in #4901. Maybe something is broken.
5. filipesilva

   assigned

   sumitarora

   on May 4, 2017
6. filipesilva

   added

   effort1: easy (hours)

   P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgent

   severity2: inconvenient

   type: bug/fix

   on May 4, 2017
7. hansl

   unassigned

   sumitarora

   on Feb 6, 2018
8. hansl commented on Jan 14, 2019

   

   hansl

   on Jan 14, 2019

   Contributor

   More actions

   This has been fixed a long time ago, never marked. If this still happens please create a new issue so we can follow up.
9. hansl

   closed this as completedon Jan 14, 2019
10. angular-automatic-lock-bot commented on Sep 9, 2019

    

    angular-automatic-lock-botBot

    on Sep 9, 2019

    More actions

    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.}
11. angular-automatic-lock-bot

    locked and limited conversation to collaborators on Sep 9, 2019