Asset Files limited?

[timschoch]

Hello

I have this wierd behaviour, that when I add more then 16 files, the gulp compile task fails.
This is my current structure:

assets/
    css/
        vendors/
            font-awesome/
                font-awesome.css
        main.css
        normalize.css
        normalize.min.css

    font/
        fontawesome-webfont.eot
        fontawesome-webfont.svg
        fontawesome-webfont.ttf
        fontawesome-webfont.woff
        fontawesome-webfont.woff2

    js/
        vendor/
            jquery.min.js
            modernizr.min.js
            prism.min.js
        leftCol.js
        main.js
        search.js
        tree.js

I've setup the theme with your generator v2.14.7 and have not modified the gulp file other
then added force to the sassdoc task. Now when I run gulp compile it creates the test project no worries. But when I add one more file (empty or not, no difference in what type of file) the gulp task just stalls out after » Folder testproject\sassdoc successfully refreshed. without an error and I have to Terminate batch job (Y/N)?

So in order to add more files, I have to remove another one (eg normalize.css) - maybe this is intended to keep our themes tidy ;)

More Infos:

• The gulp dumpJS and gulp dumpCSS tasks run fine.

• Content or Suffix of the file don't make a difference

• I'm running this in powershell as adminsitrator on a win8 machine but tried the defalt cmd too, no difference.

• yo config:

  {
      "generator-sassdoc-theme": {
          "themeName": "sassdoc-theme-ioz",
          "themeEngine": "jade",
          "author": {
          "name": "Tim Schoch"
          },
          "themeDesc": "IOZ Sassdoc Theme",
          "version": "0.0.0",
          "useExtras": true,
          "useSass": true,
          "useSassUtils": true,
          "useTaskRunner": "gulp"
      }
  }
  

[KittyGiraudel]

Super weird. @pascalduez?

[timschoch]

I've debugged it a bit and found out that it doesn't allways fail on the same part of the script. One of the last functions that gets executed properly (and I could reproduce) is listOnTimeout in timers.js. After the marked line, the script stalls most of the time.

But I did get past that once or twice and it seemed that Node got lost in an loop here. From Line 348 it would immediatly loop back to 339 (inside node.js) and do this over and over and over and over ...

... until finaly this would happend:

Does this help?

[pascalduez]

Quick reply, I don't have time right now to deeply look into this.

You mention the compile task which is responsible for generating a preview of you current theme.
It only accept SCSS files, nothing else.
So adding one or more CSS or JS file have not impact whatsoever.

You have to configure the paths, and feed it with a proper SCSS (with SassDoc comments) folder.
I would investigate this track. Looks like there's a mess with folders and you give it the current theme folder. That's why you used the force option maybe (careful with it).
If you delete a folder being currently watched Gulp won't like it.

[timschoch]

The Theme is working fine and we're using it already. I wanted to extend it with some JS fairy dust (SassDoc/sassdoc#435) and it fails if we add more files to the assets folder. With less then 16 it compiles perfectly.

[pascalduez]

Holy molly, so that's not even a Gulp thing, but more related to the assets copying functions from the theme ?
We will investigate.

Is this theme available online by any chance ?

[timschoch]

Hi @pascalduez
The theme will be so specific to our internal framework that we decided to not publish it. But I'll send it to you via mail.

[pascalduez]

Thanks @timschoch it will be helpful for replicating the issue, we keep you posted.