-
Notifications
You must be signed in to change notification settings - Fork 783
New issue
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
CLI does not parse/escape parameters correctly #1296
Comments
This should be fixed in the latest version. If it's still a problem, would you be able to create an issue with a thorough description on how to replicate this? Thanks |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Stencil version:
I'm submitting a:
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://stencil-worldwide.herokuapp.com/ or https://forum.ionicframework.com/
Current behavior:
After upgarding to version 0.16.1 (two apps, 0.15.0 and some older as well, other community members reported also strange behaviour upgrading from 0.16.0) the CLI does not parse/escape command line parameters correctly. The behaviour is experienced on Windows 10 and Linux as well (did not have the chance to verify on a mac).
The erroneous behaviour is connected the additional parameters either as part of an npm script or appended manually.
Expected behavior:
npm run-script test
executes tests just asnpm run test
where thetest
npm script is as follows:Steps to reproduce:
npm run-script test
or provide command line parameters (such as test pattern) manuallyRelated code:
npm run-script test
yields:Other information:
Jest uses the
micromatch
library that caused inconveniences with the major release of3.0.0
. It has been rolled back with Jest version 23.4 though.The text was updated successfully, but these errors were encountered: