fix(scripts): add --no-dependencies to publish:vsce and use pnpm exec - #72
Merged
Conversation
This file contains hidden or 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
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.
Summary
publish:vscescript by adding--no-dependenciesflag sovscedoes not fail on pnpm symlinkednode_modules(ELSPROBLEMSerror duringnpm list).packageandpublish:vscescripts to explicitly usepnpm execfor consistency withpublish:ovsx.Details
out/extension.jsviaesbuildandnode_modules/is excluded in.vscodeignore, bundlingnode_modulesduring packaging/publishing is unnecessary.--no-dependenciesallowspnpm run publish:vsceto publish successfully in pnpm workspace setups.Testing
pnpm run packagecompletes successfully and produces valid VSIX.pnpm run lintandpnpm run test:unitpass (199 tests).