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
It's not clear what the intent of JSDoc's Rhino compatibility is, especially when it requires a custom build. Is this legacy code, or is there a usecase I'm missing here?
The text was updated successfully, but these errors were encountered:
For some users, it may be more convenient to run JSDoc on the JDK. (I have no idea whether this is true, or how many users would prefer the JDK over Node.js.)
At some point, I plan to survey the community and find out how many people, if any, rely upon Rhino support. If nobody needs it, I'll deprecate the Rhino version. But for now, at least, we need to continue to support Rhino.
It's not clear what the intent of JSDoc's Rhino compatibility is, especially when it requires a custom build. Is this legacy code, or is there a usecase I'm missing here?
The text was updated successfully, but these errors were encountered: