Skip to content

Executables from scoped packages are wrong #1885

@SimenB

Description

@SimenB

Do you want to request a feature or report a bug?

Bug

What is the current behavior?
yarn run prints executables that can be run.

yarn run
yarn run v0.17.2
error No command specified.
info Commands available from binary scripts: @finn-no, eslint, optimize-js, rimraf, rollup, uglifyjs, @finn-no, eslint, optimize-js, rimraf, rollup, uglifyjs

(everything shows up twice as well...)

@finn-no is not a binary, @finn-no/cdn-uploader is, though (named cdn-uploader).

If the current behavior is a bug, please provide the steps to reproduce.
yarn add @finn-no/cdn-uploader && yarn run

yarn run @finn-no
yarn run v0.17.2
$ "/Users/simbekkh/repos/polyfills/node_modules/.bin/@finn-no"
sh: /Users/simbekkh/repos/polyfills/node_modules/.bin/@finn-no: is a directory
error Command failed with exit code 126.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

What is the expected behavior?
The failure is ok (should be error Command "sdaasdasd" not found., though), but the command should show up.

yarn run cdn-uploader doesn't work either.

Please mention your node.js, yarn and operating system version.
Node 6.9.1, yarn 0.17.2, macOS Sierra

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions