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.

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

chore: define expected package manager #115

Merged
merged 1 commit into from
Aug 21, 2024

Conversation

0xmichalis
Copy link
Member

For some reason, this seems to be always generated now every time I run yarn in the repo so we may as well set it.

https://nodejs.org/api/packages.html#packagemanager

@0xmichalis 0xmichalis requested a review from aspiers August 21, 2024 13:52
@0xmichalis 0xmichalis force-pushed the set-package-manager branch from 4b9eb49 to 04b9f6b Compare August 21, 2024 13:53
For some reason, this seems to be always generated
now every time I run yarn in the repo so we may as
well set it.

https://nodejs.org/api/packages.html#packagemanager
@0xmichalis 0xmichalis force-pushed the set-package-manager branch from 04b9f6b to c999b99 Compare August 21, 2024 13:55
@0xmichalis 0xmichalis changed the title Define expected package manager chore: define expected package manager Aug 21, 2024
@aspiers aspiers merged commit 888594a into ToucanProtocol:main Aug 21, 2024
1 check passed
@aspiers
Copy link
Member

aspiers commented Aug 21, 2024

BTW we should upgrade to yarn v4 everywhere. Yarn v1 is absolutely ancient.

@0xmichalis 0xmichalis deleted the set-package-manager branch August 21, 2024 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants