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
Description:
It would be really helpful to have a clear indication of the latest supported Node.js version for the Community edition of Console Ninja. This information could be displayed in the terminal or as part of the setup process to avoid confusion and improve the developer experience.
Current Issue:
I recently encountered an issue where I was using Node.js v22.9.0, which is not yet supported in the Community edition. The notification I received only mentioned that support for this version is planned for a future release, but it didn’t specify which version is currently supported. This led to some uncertainty and a bit of backtracking.
Suggested Solution:
• Display the latest supported Node.js version for the Community edition whenever a newer, unsupported version is detected.
• This could be included in the error message or as part of the project’s README or documentation page, keeping the information easily accessible for users.
Thanks for considering this suggestion!
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like.
No sure if it's a duplicated question :S
Description:
It would be really helpful to have a clear indication of the latest supported Node.js version for the Community edition of Console Ninja. This information could be displayed in the terminal or as part of the setup process to avoid confusion and improve the developer experience.
Current Issue:
I recently encountered an issue where I was using Node.js v22.9.0, which is not yet supported in the Community edition. The notification I received only mentioned that support for this version is planned for a future release, but it didn’t specify which version is currently supported. This led to some uncertainty and a bit of backtracking.
Suggested Solution:
Thanks for considering this suggestion!
The text was updated successfully, but these errors were encountered: