You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 as npm run test where the test npm script is as follows:
"test": "stencil test --spec --e2e"
Steps to reproduce:
Take a component starter with @stencil/core version 0.16.1
Execute npm run-script test or provide command line parameters (such as test pattern) manually
Related code:
npm run-script test yields:
No tests found
In C:\workspace\slds-custom-components
263 files checked.
testMatch: **/*(*.)+(e2e|spec).+(ts)?(x) - 16 matches
testPathIgnorePatterns: C:\\workspace\\slds-custom-components\.vscode,C:\\workspace\\slds-custom-components\.stencil,C:\\workspace\\slds-custom-components\\node_modules,C:\\workspace\\slds-custom-components\\dist,C:\\workspace\\
slds-custom-components\\www - 60 matches
Pattern: run-script - 0 matches
Other information:
Jest uses the micromatch library that caused inconveniences with the major release of 3.0.0. It has been rolled back with Jest version 23.4 though.
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
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: