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

Remove yarn, just adds complexity #340

Open
bhouston opened this issue Jan 22, 2024 · 1 comment · May be fixed by #341
Open

Remove yarn, just adds complexity #340

bhouston opened this issue Jan 22, 2024 · 1 comment · May be fixed by #341
Labels
enhancement New feature or request

Comments

@bhouston
Copy link

Describe the feature you'd like:

I would propose we remove yarn. NPM is faster and more reliable than it was years ago. Yarn just adds an unnecessary dependency and a global install. Also there are multiple versions of yarn and it can be confusing as to which to you as they are not compatible with each other.

Suggested implementation:

I have a branch that removes yarn and everything appears to work.
@bhouston bhouston added the enhancement New feature or request label Jan 22, 2024
@CodyJasonBennett
Copy link
Member

Maybe we're missing "packageManager": "yarn@1.22.19",, but is this related to the broken behavior you described in Discord with types? I'm not opposed to switching back to NPM, but it hasn't been an emergency for us.

@CodyJasonBennett CodyJasonBennett linked a pull request Jan 23, 2024 that will close this issue
chore: straight forward replace of yarn with npm #341
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: straight forward replace of yarn with npm bhouston/three-stdlib
2 participants
@bhouston @CodyJasonBennett