-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Added the minimum supported node.js version to the support page #1733
Added the minimum supported node.js version to the support page #1733
Conversation
✅ Deploy Preview for expressjscom-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea, I support this addition. I have not confirmed the actual version numbers for EOL, but LGTM
de/support/index.md
Outdated
| **v0.14.x**{: .eol } | December 2010 | December 2010 | | ||
| Major Version | Minimum Node.js Version | Support Start Date | Support End Date | | ||
| -- | -- | -- | -- | | ||
| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html) | 18.0.0 | September 2024 | **ongoing**{: .supported } | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it funny to anyone else that we called this translated but it is not? Why even have this copy instead of just falling back to the english version if it is just english anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was done this way because it's how translations work on the page. If we redirected to the English page, we would make the user click again to return to the language they were in before. There is a lot of improvement in the translation process.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, and I agree this would be awesome to improve upon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The easiest way is to migrate to a more modern technology like starlight or docusaurus, which have better support for i18n and we wouldn't have to be copying the content like we're doing now, or a slightly more complicated approach would be to have the translations done by an AI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
docusaurus gets my vote.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some very promising tools out there to translate the content with AI. If you are interested take a look at for example: https://github.com/midday-ai/languine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Phillip9587, there is an issue about that, in case you want to participate,
and for the website migration, there is this issue.
@Phillip9587 thanks |
Added the minimum supported node.js version to the support page. Please correct me if I'm wrong about the minimum versions for the 3.x, 2.x, 1.x and 0.14.x release lines.
Preview: https://deploy-preview-1733--expressjscom-preview.netlify.app/en/support/