Scripty scripts are missing from the output of npm run

[deanrad]

For discoverability, developers expect available scripts to be listed from npm run. It appeared to me that scripty scripts are not - is that expected behavior?

Dean

[searls]

To try and get clarity here, this is what I get when I run npm run without args on this branch of one of my projects:

$ npm run
Lifecycle scripts included in testdouble:
  test
    scripty
  preversion
    scripty
  postversion
    scripty
  version
    scripty
  prepublish
    scripty

available via `npm run-script`:
  clean:dist
    scripty
  clean
    scripty
  compile:node
    scripty
  compile:test
    scripty
  compile:browser
    scripty
  compile
    scripty
  test:cover:instrument
    scripty
  test:cover:run
    scripty
  test:cover:report
    scripty
  test:cover
    scripty
  test:browser
    scripty
  test:example:webpack
    scripty
  test:example:node
    scripty
  test:example:lineman
    scripty
  test:example
    scripty
  test:all
    scripty
  test:ci
    scripty
  version:write
    scripty
  version:changelog
    scripty

Since npm owns the npm run command, I'm not sure what I could do to override its behavior short of wrapping the npm bin, which nobody would get behind.

Do you have any insight into how this could be improved cleanly?

[zeke]

Shameless self-promotion and not a solution per se, but I prefer npe to npm run.

npm i -g npe && npe scripts

[deanrad]

Closing on account of my not remembering what I thought the problem was with that output, which LGTM.

[searls]

Haha ok dean

On Jul 25, 2016, at 13:41, Dean Radcliffe [email protected] wrote:

Closing on account of my not remembering what I thought the problem was with that output, which LGTM.

―
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.