Skip to content

Migrate from yarn to npm#970

Draft
vezwork wants to merge 3 commits intomainfrom
migrate-yarn-npm
Draft

Migrate from yarn to npm#970
vezwork wants to merge 3 commits intomainfrom
migrate-yarn-npm

Conversation

@vezwork
Copy link
Copy Markdown
Member

@vezwork vezwork commented May 6, 2026

As discussed in #801 and in conversation with @juliasilge and @cscheid, it is likely more stable and less error-prone to switch this monorepo from using yarn to npm.

In #801, I was unable to work past yarn+monorepo issues blocking me from updating a package. That was my original motivation to consider switching.

In this PR I used Claude to migrate from yarn to npm. I am able to update codemirror/autocomplete, take the main code change from #801, and build locally, which is a success!

On the other hand, CI is failing and I don't understand why, so that is blocking this PR.

@posit-snyk-bot
Copy link
Copy Markdown
Contributor

posit-snyk-bot commented May 6, 2026

⚠️ Snyk checks are incomplete.

Status Scan Engine Critical High Medium Low Total (0)
⚠️ Open Source Security 0 0 0 0 See details
⚠️ Licenses 0 0 0 0 See details

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@vezwork vezwork marked this pull request as draft May 6, 2026 13:53
@vezwork vezwork marked this pull request as draft May 6, 2026 13:53
@vezwork vezwork force-pushed the migrate-yarn-npm branch from d93e42d to 81fbf58 Compare May 6, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants