Repository navigation
show recommended node version even if engines define something else #3167
Description
Describe the feature
https://github.com/lorypelli/in-container/blob/main/package.json#L6-L8
https://github.com/lorypelli/in-container/blob/main/src/cli.ts#L50-L52
show the recommended node version based on from which version the function is available and show it in the website
in my case:
min: >=14.18.0
recommended: >=16.17.0 <17.0.0 || >=18.3.0
Additional information
- Would you be willing to help implement this feature?
Final checks
- Read the contribution guide.
- Check existing issues.
Activity
ghostdevv commentedon Aug 11, 2026
We do show it on the sidebar!
lorypelli commentedon Aug 12, 2026
Nope, that's the version from the engines field, but cli.ts in this case doesn't support it
lorypelli commentedon Aug 12, 2026
Check the code of cli.ts
gameroman commentedon Aug 12, 2026
How do you want npmx to detect the recommended version?
If there was some standard
"recommendedEngines"field, we could display itlorypelli commentedon Aug 12, 2026
Yeah, that could be good, but it doesn't exists, then, manually code checking if a node built-in function has ranges (if you see cli.ts I explicitely throw an error with the ranges, but that's up to the developer unfortunately), any ideas, maybe just check built-in node functions used in the package
gameroman commentedon Aug 12, 2026
That'd be difficult probably since it'd require checking every single file which would not be very efficient
I think standardizing something like
"recommendedEngines"would be simplerI've added
needs discussionso lets see what others thinkghostdevv commentedon Aug 12, 2026
The fact that you're throwing an error suggests that in fact it's not recommended, it's required - in which case
enginesis the correct field?