Getting command line too long while running grunt jsdocs as i am having large set of file, i also checked #51,#59 but not able to resolved.

[junedansari]

Hi,
Thanks in advance .
Please help me to resolve my below given problem
Getting command line too long while running grunt jsdocs as i am having large set of file, i also checked #51,#59 but not able to resolved.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[krampstudio]

There are multiple solution:

1. Use a real operating system 😉
2. Set the file pattern into a jsdoc config
3. Wait for an option that will prevent expanding the files and gives the pattern as it is to jsdoc.

Obviously the third is the best but I won't have the time to do it before a few weeks

[junedansari]

thanks for reply..
i have tried, failing to execute a long string command on windows as you suggest to use real operating system ;) but icant i have to live with windows
plz help me reduce command line argument.

[junedansari]

Hi,
My jsdoc conf.json as given below
{
"dist": {
"src": [
"README.md",
"app/.js",
"app/auth/__/.js",
"app/ui-components//.js",
"app/config/.js",
"app/main/.js",
"app/menu/core/.js",
"app/pb-map-info-handler/.js",
"app/menu/.js",
"app/common/*.js",
"!app//.md",
"app/pb-localisation/.js"
],
"tags": {
"allowUnknownTags": true,
"dictionaries": [
"jsdoc",
"closure"
]
},
"templates": {
"cleverLinks": false,
"monospaceLinks": false
},
"plugins": [
"angular-jsdoc"
],
"options": {
"destination": "build/doc/html",
"template": "templates/default",
"encoding": "utf8",
"recurse": true
}
}
}

here large set of file to create jsdoc, plz let me know is there a way to break for set of file then further for next set of files so that all js files will be documented.

[krampstudio]

if yoy have a jsdoc.conf file, then do not use the src property in you grunt config. this should do it.

[junedansari]

But i am having some other conf file for protractor/karma and for some other plugin.Using load-grunt-configs for same.

[krampstudio]

if you have defined your target sources into the jsdoc config file, then you don't need the src propery into the grunt jsdoc configuration:

jsdoc : {
   dist : {
       options : {
          destination : 'doc',
          configure : 'jsdoc.conf.js'
       }
   } 
}

Without the src property in the jsdoc plugin configuration the error should go away. The error is produced by grunt expanding the file pattern.

[junedansari]

Thank you so much for your reply.
Highly appreciated.

Here is jsdoc.conf.json and i have not modify it
{
"tags" : {
"allowUnknownTags" : true
},
"plugins" : ["plugins/markdown"],

"templates" : {
    "cleverLinks"           : false,
    "monospaceLinks"        : false,
    "dateFormat"            : "ddd MMM Do YYYY",
    "outputSourceFiles"     : true,
    "outputSourcePath"      : true,
    "systemName"            : "DocStrap",
    "footer"                : "",
    "copyright"             : "DocStrap Copyright © 2012-2014 The contributors to the JSDoc3 and DocStrap projects.",
    "navType"               : "vertical",
    "theme"                 : "cosmo",
    "linenums"              : true,
    "collapseSymbols"       : false,
    "inverseNav"            : true,
    "highlightTutorialCode" : true,
    "protocol": "fred://"
},
"markdown"  : {
    "parser"   : "gfm",
    "hardwrap" : true
}

}
and if i have removed my src properties then i am getting error as "No Source files defined" while run grunt jsdoc

[junedansari]

@krampstudio
if i use recurse true
then getting error as FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

ur help wud be highly appreciated.