Repository navigation
aliases aren't CLI firendly #23
Description
I'm currently working on a CLI that's building off of this work, and I've found that the aliases are relatively unfriendly to CLIs. I've never seen a Node.js native command line tool that uses underscores, and am finding myself having to alias them which provides a less cohesive experience than I'd like.
I'd like to request that more CLI-friendly aliasing be introduced for the lts variants.
Activity
wesleytodd commentedon Feb 7, 2022
Those aliases were defined by the package maintenance working group, not this tool. I do agree that the aliases keys are not super friendly, maybe we could change how they are defined in the spec and then release v2?
bnb commentedon Feb 7, 2022
+1 I'm happy to change how they're defined in the spec and release an update.
shadowspawn commentedon Feb 7, 2022
Are you talking about changing the node namespace aliases in https://github.com/nodejs/package-maintenance/blob/main/docs/PACKAGE-SUPPORT.md ?
They are being used in
package-support.jsonfiles and in code outside the node organisation (e.g. https://github.com/tj/n/blob/392f9ab7d8434f9a73386a6cea055fafb7b37f86/bin/n#L305). Changing the node namespace aliases for a little more CLI friendliness seems expensive.Perhaps you are weighing all of that, or perhaps it is some other definition you are talking about. I wanted to clarify because it seemed very casually discussed. 🤭
bnb commentedon Feb 7, 2022
I am talking about those. I'll be frank, I don't think that they're a good API and should not be used in end-user APIs that module maintainers are presented, as this module does. If changing them is not something that is possible, I'll strongly recommend we abandon using them.
dominykas commentedon Feb 12, 2022
We should add this to the PM WG meeting agenda.
wesleytodd commentedon Oct 19, 2023
Do we still think this is an issue? I can probably make the next PMWG meeting on the 24th if we want to discuss?
bnb commentedon Oct 25, 2023
IMO yes. Having non-CLI-friendly names is borderline a non-starter.
wesleytodd commentedon Oct 26, 2023
Going to close this and point to your PR in the PMWG: nodejs/package-maintenance#581
Once that is resolved I can update the package and release a new major with the new aliases.