search

sezna / nps

NPM Package Scripts -- All the benefits of npm scripts without the cost of a bloated package.json and limits of json
MIT License
1.43k stars 93 forks source link

Add npsl (nps list) binary #123

Open kentcdodds opened 7 years ago

kentcdodds commented 7 years ago

Got this idea from a tweet from @marcusoftnet. Basically the same kind of experience as ntl:

zjjq7vi

That'd be pretty awesome. Anyone wanna take this on?

Miklet commented 7 years ago

It would be great to have this feature. Did you think on any possible solution? I just saw that ntl is using inquirer and we could possibly use it too.

kentcdodds commented 7 years ago

Yep, that's what I had in mind as well! 👍

Miklet commented 7 years ago

I am going to work on this feature in my leasure time.

Miklet commented 7 years ago

Since I do not have much time lately to actively take part in nps I leave this feature unassigned. Maybe someone will want to make it shine 😄

hmerzin commented 6 years ago

Hi, I've been working on this and was wondering where I could get a list of the package scripts or a parsed config file? So far the only way I was able to get it was by calling parse on process.argv.split.... like in nps.js. I did see the function getAvailableScripts in index.js, but haven't found a config reference to the config to pass into it.

Thanks, Harry

ryansully commented 5 years ago

There is already a project that seems to do this, https://github.com/siddharthkp/nps-i. It was even added to the README in https://github.com/sezna/nps/pull/178.