You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of an automated process, jsdoc-api writes source code to the system tmp folder (returned by os.tmpdir()) then parses it using jsdoc -X.
However, some users are reporting that jsdoc-api randomly fails with There are no input files to process yet a reboot of the machine fixes it.
It's because the system temp folder path occasionally features a leading underscore, e.g.
/var/folders/_9/nl_3vwh14lx9325r9cn6s08s96pd8g/T/
If there is a leading underscore in any part of the working directory tree, jsdoc fails. Could this default behaviour be reconsidered please? It leads to confusing, intermittent bugs.
The text was updated successfully, but these errors were encountered:
As part of an automated process, jsdoc-api writes source code to the system tmp folder (returned by
os.tmpdir()
) then parses it usingjsdoc -X
.However, some users are reporting that jsdoc-api randomly fails with
There are no input files to process
yet a reboot of the machine fixes it.It's because the system temp folder path occasionally features a leading underscore, e.g.
If there is a leading underscore in any part of the working directory tree, jsdoc fails. Could this default behaviour be reconsidered please? It leads to confusing, intermittent bugs.
The text was updated successfully, but these errors were encountered: