yvm exec incorrectly expands glob about yvm

[iamogbz]

@noahnu I'm not sure I understand your use case here or at least I could not reproduce the issue. yvm exec is supposed to be equivalent yarn, and I don't think yarn my-script.js works.

Also if I have something like

// package.json
  "scripts": {
    "say": "echo"
  }

then I get

$ yvm exec say "some/**/*.js"
yarn run v1.22.4
$ echo 'some/**/*.js'
some/**/*.js
Done in 0.09s.

[noahnu]

I was modelling it after nvm exec with stylelint's glob option. Can put together a better repro in a bit

[noahnu]

Hmm.. you're right. I still think there's an issue here, but my steps to reproduce are incorrect. I encountered this when trying to use yvm exec to run stylelint. The glob was being expanded. When I switched to use nvm exec, it worked.

I'll try put together a better example with stylelint directly.

[iamogbz]

I see what you mean

$ yvm exec fake './*.js'
yarn run v1.22.4
$ /workspace/yvm/node_modules/.bin/fake ./fake.js
[
  '/home/gitpod/.nvm/versions/node/v12.18.3/bin/node',
  '/workspace/yvm/node_modules/.bin/fake',
  './fake.js'
]
Done in 0.15s.

vs

$ yarn fake './*.js'
yarn run v1.22.4
$ /workspace/yvm/node_modules/.bin/fake './*.js'
[
  '/home/gitpod/.nvm/versions/node/v12.18.3/bin/node',
  '/workspace/yvm/node_modules/.bin/fake',
  './*.js'
]
Done in 0.14s.

Both of those were run by yvm and it seems like the culprit is, as you pointed out, the bash script expansion. 🐟 shell does not have this problem, proving without a doubt that it is the BASST!

[iamogbz]

Wrapping it in quotes does look like it'll fix this and probably is a breaking change to modify this behaviour 🤔

[yvm-bot]

🎉 This issue has been resolved in version 4.0.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀