fix: npx vsce package should work #120
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Skipped PR review on 90bf532 because no changed files had a supported extension. If you think this was in error, please contact us and we'll fix it right away. Something look wrong? You can customize Ellipsis by editing the ellipsis.yaml for this repository. Generated with ❤️ by ellipsis.dev |
SoonIter
force-pushed
the
fix/vsce-pck
branch
from
90bf532 to
539c16e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@types/vscodehas to matchengines: vscodeusing pnpm as pkg manager should have no dependencies and bundle everything, because
vsce packageusenpm listrather thanpnpm list.vscodeignoreto reduce pkg installation sizeReview steps
npx @vscode/vsce@latest packageinstall the extension from
.vsixand check the features