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
Have a package with unit-jest and another cli plugin.
Create a script which contains: vue-cli-service test:unit --skip-plugins ANY_INSTALLED_PLUGIN_OTHER_THAN_UNIT_JEST
Run the script: npm/yarn run SCRIPT_NAME
What is expected?
--skip-plugins should in my opinion only be used in @vue/cli-service. As this argument is not relevant for any plugin, correct me if I am wrong.
So the argument and it's value should be removed from args and rawArgv
What is actually happening?
--skip-plugins are not removed from args and rawArgv. In the unit-jest plugin, the rawArgv are passed directly to jest. Which causes jest to raise an error
So I think that we should remove --skip-plugins from the arguments. Another solution could be that the unit-jest plugin is changed to filter the arguments there. But I think we should only go for the latter, if you think that there could be any plugin that would require/use the --skip-plugins argument.
The text was updated successfully, but these errors were encountered:
Version
5.0.0-rc.2
Environment info
Steps to reproduce
unit-jest
and another cli plugin.vue-cli-service test:unit --skip-plugins ANY_INSTALLED_PLUGIN_OTHER_THAN_UNIT_JEST
npm/yarn run SCRIPT_NAME
What is expected?
--skip-plugins should in my opinion only be used in @vue/cli-service. As this argument is not relevant for any plugin, correct me if I am wrong.
So the argument and it's value should be removed from
args
andrawArgv
What is actually happening?
--skip-plugins are not removed from
args
andrawArgv
. In theunit-jest
plugin, therawArgv
are passed directly tojest
. Which causesjest
to raise an errorSo I think that we should remove --skip-plugins from the arguments. Another solution could be that the unit-jest plugin is changed to filter the arguments there. But I think we should only go for the latter, if you think that there could be any plugin that would require/use the --skip-plugins argument.
The text was updated successfully, but these errors were encountered: