feat: update project to use npm workspaces #33
Merged
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.
Update the package manager in the extension folder to use
npm. By default, the@vscode/vsce(extension packager) tool does not support pnpm, causing a required dependency upgrade when building the extension.This is not strictly related to #32, but might cause potential inconsistencies. For that reason, I included this PR as part of this issue.
Update
After checking it with @ereslibre, I took the opportunity to update the project to use
npm. I configured the workspace and move all the current projects (cli and extension) to thepackagesfolder.Each project uses now their own package.json and share a workspace to simplify dependency management and configuration.