"ng generate module/component" doesn't work as expected

Please provide us with the following information:

OS?

• Windows 10

Versions.

@angular/cli: 1.0.0-rc.0                      
node: 7.5.0                                   
os: win32 x64                                 
@angular/animations: 4.0.0-rc.1               
@angular/common: 4.0.0-rc.1                   
@angular/compiler: 4.0.0-rc.1                 
@angular/core: 4.0.0-rc.1                     
@angular/forms: 4.0.0-rc.1                    
@angular/http: 4.0.0-rc.1                     
@angular/platform-browser: 4.0.0-rc.1         
@angular/platform-browser-dynamic: 4.0.0-rc.1 
@angular/platform-server: 4.0.0-rc.1          
@angular/router: 4.0.0-rc.1                   
@angular/cli: 1.0.0-rc.0                      
@angular/compiler-cli: 4.0.0-rc.1             

Repro steps.

1. run ng g m my-module - [ will work as expected ]

2. decide that you want a module and routes, so run ng g m my-module --routing

3. get asked if you want to override the old module, hit y

4. get sad because the routing file was not created 😢

5. decide that you want to add a component matching the module name, so run ng g c my-module

6. get sad again because the new component got not added to your new my-module.module.ts but to your app.module.ts 😢

7. be happy again because the Angular CLI is such a timesaver for most parts 😄👍

The log given by the failure.

---

Mention any other details that might be useful.

Thanks to the team for all the effort ❤️

---

[delasteve]

@bboehm86, The issue is that by not specifying --flat the CLI thinks that it is going to create a folder and begin looking in the parent folder to that component. Part of me wants to say this is the correct functionality.

@markgoho and @AlvaroOrduna, you will need to be more specific on the file you wish to use for your module.

@markgoho: ng g component home --module=home/home.module @AlvaroOrduna: ng g component back\home --module back\back.module

That said, I’ll look into creating a PR for both of these issues. I’ll let the CLI team determine what the correct functionality is.

Side note: I incorrectly thought my other PR, #5218, fixed this issue. It does not.

[markgoho]

I’m having this issue, too. All new components are being added not to the nearest module, but to the root app.module. This is not a new feature…but it does appear to be broken. I can confirm that @bboehm86 suggestion of my-module/my-module --flat does produce the desired outcome of generating a component and having the CLI add it to the module in that director.

After generating a new module ng g module home the command ng g component home --module=home produces the following error:

Error: EISDIR: illegal operation on a directory, read
    at Object.fs.readSync (fs.js:656:19)
    at tryReadSync (fs.js:457:20)
    at Object.fs.readFileSync (fs.js:494:19)
    at Class.afterInstall (C:\Users\Nella\Documents\GitHub\pccRegistration\node_modules\@angular\cli\blueprints\component\index.js:207:34)
    at tryCatch (C:\Users\Nella\Documents\GitHub\pccRegistration\node_modules\rsvp\dist\rsvp.js:538:12)
    at invokeCallback (C:\Users\Nella\Documents\GitHub\pccRegistration\node_modules\rsvp\dist\rsvp.js:553:13)
    at publish (C:\Users\Nella\Documents\GitHub\pccRegistration\node_modules\rsvp\dist\rsvp.js:521:7)
    at flush (C:\Users\Nella\Documents\GitHub\pccRegistration\node_modules\rsvp\dist\rsvp.js:2373:5)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)