Resolve existing package managers issues (including pnpm)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- tooling
Research direction
Locate the generator code that creates the package.json manifest for bundled extension projects, then trace how the selected package manager affects that output. Confirm that generated manifests include dependencies: false for bundled configurations across the supported package managers, and verify the generated output with the project's existing tests or checks.
Written by the indexing model from the issue text.
Description
When initializing a bundled extension project, the generator does not automatically include dependencies: false in the generated package.json manifest.
Most modern package managers (specifically pnpm, but also npm and yarn) continue to include a node_modules folder or resolve dependencies (npm list --depth 9999) unless explicitly told otherwise (dependencies: false). For extensions that are bundled (e.g., into dist/extension.js), including these dependencies in the VSIX is unnecessary and increases the package size and runs the npm list --depth 9999 command.
Proposed Change
Update the generator to include dependencies: false in the manifest by default whenever a user selects a "bundled" project configuration. This should apply regardless of the chosen package manager.
Context & Dependencies
https://github.com/microsoft/vscode-vsce/pull/1257
While the PR above addresses a race condition to ensure dependencies: false is respected reliably by vsce, the generator should be updated independently to support this field.
Future Work
Once the PR is merged, we should also look into adding support for runPrepublish option specific to each package manager (e.g., pnpm run vscode:prepublish).
- Dominant language
- JavaScript
- Stars
- 1.6k
- Forks
- 262
- Avg merge
- 15d 22h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-generator-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/vscode-generator-code#597 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-generator-code#575 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 56/100
-
DeprecationWarnings Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in microsoft/vscode-generator-code
Similar issues
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·
-
bug p1 tools
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
factory-active factory-automatic task-bug-reproduction-cannot-reproduce task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 84/100