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
Just as a matter of housekeeping I suggest this get updated to ">=18.0.0" or preferably ">=20.0.0". The current NodeJS version is v24.
All reasoning applies to other tickets suggesting dependency updates...
This is in part to protect anyone using the package but actually only applies people using very old legacy NodeJS.
A DS user/developer on an older Node needs to move themselves forward or else we might hear from them about issues that are no longer valid.
Updated sub-dependencies in this package may not be able to run in legacy Node, causing crashes or unexpected behavior. Ref Doc project dependency issues #277
Deployment of this doc package locally or online with legacy Node leaves the installation vunerable to old security issues - that can reflect badly on DS itself.
This is also a marketing concern - the appearance of support for old platforms makes this platform look dated.
This simple change that doesn't affect any developer with current tooling - there's no real reason not to do this.
package.json includes:
Just as a matter of housekeeping I suggest this get updated to ">=18.0.0" or preferably ">=20.0.0". The current NodeJS version is v24.
All reasoning applies to other tickets suggesting dependency updates...