npm WARN deprecated har-validator@5.1.5: this library is no longer supported
3:36 AM
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
3:36 AM
npm WARN deprecated morsify@2.4.0: WARNING: This project has been renamed to morse-decoder. Install using morse-decoder instead.
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
I’ll have to disagree with that as a general suggestion and would say it depends upon a few things the simplest being have you installed all or some of those packages directly? If so then you may be able to update them.
The second one and most important is, what does this app do for you? If it is a toy and it doesn’t matter if it stops running or is out of commission at some point in the future do you care?
If it generates income or is otherwise useful then time spent fixing the issue now will likely save you time and effort in the future. Take for example the morsify warning, it has been “renamed” can you use the renamed one? Problem solved.
Unsupported libraries will no longer have bug fixes applied and may rely on old tech. The day where that interferes with (or simply makes it harder/impossible) to use something newer will eventually arrive.
While using unsupported packages is never reccomended, these are likely dependencies and can only be changed by the developer of the package that depends on them.