Missing files when using angular-fullstack:route

[thomasvnl]

When creating a route with angular-fullstack:route, within the environment mentioned below, the generator does not produce an html (or pug in this case) and css (or less in this case) file, which according to this documentation it should do. Also, the generated component tries to require a html file when pug is selected for the project.

Anyone experiencing the same issue(s)?

Environment generator-angular-fullstack | 4.1.0 Node | 6.9.1 npm | 3.10.9 Operating System | Windows 10

Project Settings Transpiler | Babel Markup | Pug CSS | LESS Router | ui-router Client Tests | Mocha DB | MongoDB Auth | Y SocketIO | Y

[Awk34]

Would you post all the file names that do get created? for sanity's sake. A screenshot of your terminal while generating might be helpful too.

[thomasvnl]

@Awk34 I've just run the command and this is it's output, which corresponds with the files being created:

C:\projects\booky\client>yo angular-fullstack:route test

Just found a `.yo-rc.json` in a parent directory.
Setting the project root at: C:\projects\booky
? What module name would you like to use? bookyApp.test
? Where would you like to create this route? client/app/
? What will the url of your route be? /test
   create client\app\test\test.routes.js
   create client\app\test\test.component.js
   create client\app\test\test.component.spec.js
   create client\app\test\test.less

In the parent of this component, you should now import this component and add it as a dependency:

    import TestComponent from './test/test.component';
    ...
    export angular.module('myParentModule', [TestComponent]);

//offtopic Also, could you explain what the last part means of "In the parent of this component"? Is that necessary or is it something you might want to do when using sub-components? If it is necessary, where would I put this in a fresh of the shelve generated app?

[aniknafs]

Looks like the .pug files don't generate because generator-ng-component had .jade as template. Should be fixed when ng-component is updated.

[Awk34]

Please make sure to use generator-ng-component@1.0.5 or above. This will be enforced in the next release of the generator.