Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Migrate repository from Yarn to npm

Open
  • Is something wrong?
#152 0 comments 2 reactions 2 assignees View on GitHub

@rzhao271 is already working on this.

Since Mar 17, 2026.

  • #153 by @copilot-swe-agent — closed without merging

Assessment

This issue has not been assessed yet.

Description

This repository appears to use Yarn (yarn.lock present). Please migrate package management from Yarn to npm.

Scope:

  • Replace Yarn commands/workflows with npm equivalents.
  • Generate and commit package-lock.json.
  • Remove yarn.lock and Yarn-only config files if they are no longer needed.
  • Update CI/scripts/docs to use npm (for example, npm ci and npm run <script>).

Acceptance criteria:

  • No remaining Yarn usage in scripts, docs, or CI pipelines.
  • package-lock.json is committed and up to date.
  • Build/test workflows pass after migration.
Dominant language
JavaScript
Stars
837
Forks
811
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-remote-try-node

All issues in microsoft/vscode-remote-try-node

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.