Skip to content
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

Unique package manager #406

Open
alcpereira opened this issue Jan 5, 2025 · 1 comment · May be fixed by #407
Open

Unique package manager #406

alcpereira opened this issue Jan 5, 2025 · 1 comment · May be fixed by #407

Comments

@alcpereira
Copy link
Contributor

Currently the repo uses both npm and pnpm, and also invites the contributors to use their preferred one.
This is not common and can lead to various issues.

As the CI uses pnpm and pnpm is much faster than npm, I would recommend using pnpm only and remove completely npm mentions from the repo.
@alcpereira alcpereira linked a pull request Jan 7, 2025 that will close this issue
Open
@KyleDL101
Copy link
Contributor

Yeah it looks like the build agent (for PR checks at least) uses pnpm so I don't really see a need for npm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: use pnpm instead of npm alcpereira/www
2 participants
@alcpereira @KyleDL101