We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm run
Describe the bug
Thanks for creating a fork!
I was playing with npm run command. To be honest, I do not use NPM regularly, might be this is expected:
npm run test -- --version -> yarn run test --version (ok) npm run test -- -v -> yarn run test -- -v (?)
npm run test -- --version
yarn run test --version
npm run test -- -v
yarn run test -- -v
npm test -- --version -> yarn test -- --version (?) npm test -- -v -> yarn test -- -v (?)
npm test -- --version
yarn test -- --version
npm test -- -v
yarn test -- -v
Feels like -- should be skipped in all yarn commands. Or did I miss something?
--
yarn
Package & Environment Details
"@armano/npm-to-yarn": "^1.1.3"
The text was updated successfully, but these errors were encountered:
fix: add test cases for reported issues
bcef280
- #6 - #7
fixed in npm-to-yarn
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
Thanks for creating a fork!
I was playing with
npm run
command. To be honest, I do not use NPM regularly, might be this is expected:npm run test -- --version
->yarn run test --version
(ok)npm run test -- -v
->yarn run test -- -v
(?)npm test -- --version
->yarn test -- --version
(?)npm test -- -v
->yarn test -- -v
(?)Feels like
--
should be skipped in allyarn
commands. Or did I miss something?Package & Environment Details
"@armano/npm-to-yarn": "^1.1.3"
The text was updated successfully, but these errors were encountered: