This project doesn't solve any problems about nps HOT 3 CLOSED

Just because p-s allows to have a description, it's already a problem solver for me.

When you have a project with a lot of tasks, and then a new person joins your team, having a description is really good to quickly explain the reason of a task and what it does without reading the scripts.

from nps.

@tleunen interesting. I guess we are lucky that no newcomers in our company needed such help (or maybe our scripts are simple and don't even count). Could you point me to a project where p-s really shines as a tool that helps newcomers? I really want to understand your situation since I am the guy who introduces people to JS stuff in my company.

Could you also share some thoughts on the other two problems I have mentioned?

Thought I can't remember which projects they were, I do remember that suggestions similar to your prefixing being rejected in a few CLI projects for the reasons I have mentioned. Do you also see this as a feature that allows bad practices or do you disagree?

How about the shape of the configuration? Wouldn't you rather a flat configuration like npm's?

from nps.

I've updated the video with an annotation indicating that you shouldn't actually use the aliases in your package-scripts.js configuration. I agree with you that it's better to be hard coded and only really used when you're running scripts yourself.

As for everything else you talked about, feel free to disagree and not use this project. But please don't be rude. Just because you don't think it's useful doesn't mean you have to file an issue to show how much you think the project is useless. Just move on.

from nps.