-
Notifications
You must be signed in to change notification settings - Fork 591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is timeoff-management usable with Node v16? #528
Comments
No, this software only works correctly with nodejs 13 - so even with 14, the migration of databases fails (but the rest seems to work fine). Yes, nodejs 13 is completely unsupported. And it also needs python2 (for dependencies) - which is also completely unsupported since 2020. And the dependencies which this tool uses have numerous known security vulnerabilities. So it basically a no go to install this thing in any production environment nowadays. Which is rather bad because the actual software does a lot of things right (and simple). @vpp are there any plans to get the dependency stuff fixed and migrate to any supported nodejs version? At the moment, only nodejs 18 and 20 are actively supported by nodejs upstream. 16 still receives minimal (maintenance) support. One of the bigger problems I see at the moment is sequelize(-cli). It has a lot of the weird dependencies (holding everything back) but which also changed the API in the most recent versions. But if you want to migrate a already existing installation to a new nodejs version (to nodejs 18.x) then it is enough to remove package-lock.json and apply following change
and run:
Most of the things will work fine but the
|
@vpp I also had issues with Node 16 like #489, but I would to upgrade like soon, so I can use other node apps on the same machine that expect v16. Did you test 16 already? I will send more logs later on, but maybe you already have checked it yourself. :) Thank you!
The text was updated successfully, but these errors were encountered: