Skip to content
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

Clearer error message for publish when passing both packagePath and target #764

Closed
wandyezj opened this issue Aug 16, 2022 · 1 comment · Fixed by #765
Closed

Clearer error message for publish when passing both packagePath and target #764

wandyezj opened this issue Aug 16, 2022 · 1 comment · Fixed by #765
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug released

Comments

@wandyezj
Copy link
Contributor

When running the following:

./node_modules/.bin/vsce publish -target web --packagePath ./dist/extension.vsix

The following error message is produced:

ERROR Both options not supported simultaneously: 'packagePath' and 'target'.

This error message was not sufficient for me to figure out how to fix the issue. Since I want to apply the 'target' parameter.

It would be convenient if this error message was more actionable and specified how to fix the error. In this case by passing the target flag in the package step.

Proposed new error message:

ERROR 'packagePath' specifies publishing an already created package. If using packagePath the 'target' must be specified when the package is created with vsce package

It would also be helpful to specify this in the vsce publish --help for the target parameter or the packagePath parameter.

@joaomoreno joaomoreno self-assigned this Aug 19, 2022
@joaomoreno joaomoreno added the bug Issue identified by VS Code Team member as probable bug label Aug 19, 2022
@github-actions
Copy link

🎉 This issue has been resolved in version 2.10.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants