New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switch the package manager to npm #7

Open

yhatt opened this issue Jul 30, 2023 · 0 comments

Member

yhatt commented Jul 30, 2023

Marp team is considering to switch the default package manager for the whole of Marp project from yarn 1 to npm.

Purpose

Avoiding a bug that remain in Yarn 1 related to complex dependency resolution
- The problem Warning: pattern is trying to unpack in the same destination yarnpkg/yarn#4812 is currently becoming appearent in many JS tools.

Make it easier for developers who want to contribute to the Marp project to set it up
- npm is the default Node.js package manager
- We have considered upgrading yarn or adopting pnpm, but npm is also evolving flexibly by picking up the feature of each tool. There is small positive impact of using an alternative package manager for now and future.

yhatt mentioned this issue

Switch package manager from yarn to npm marp-team/marpit#391

Merged

yhatt mentioned this issue

Switch package manager from yarn to npm marp-team/marp-core#379

Merged

yhatt mentioned this issue

Switch package manager from yarn to npm marp-team/marp-cli#607

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment