-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
refactor: migrate to Yarn Berry (v3.2.1) #8764
Conversation
@acid-chicken I'd personally like your feedback on this PR first if you don't mind, as you've been the most involved with Yarn Berry discussion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your work.
I believe that by using the node_modules linker, we can upgrade without facing most of the problems, so I think this PR is fine with the current policy for now, regardless of whether we move to PnP mode in the future or not.
Also, since Yarn berry has built-in monorepo management system called workspaces, so it would be great (and probably easy) to also improve the current situation, which is awkwardly realized by scripts/install-packages.js
and so on.
Also, since there are opinions like #5858 (comment), it would be better if Corepack could be used as a boot loader for Yarn berry (instead of placing |
Running |
|
@acid-chicken yep! |
Seems like the labeler bot adds back removed labels every commit ^^" |
Done! |
I assume |
developに追従した |
マージしちゃう? |
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
yarn install --immutableであれば1GiBで足りるかも |
そもそもproductionのビルドって yarn v1 版でも1GBで足りるんだっけ?vite入ったから行ける? |
無理だった |
packages/backend/package.json
Outdated
"got": "12.5.2", | ||
"hpagent": "1.2.0", | ||
"ioredis": "4.28.5", | ||
"ip-cidr": "3.0.10", | ||
"is-svg": "4.3.2", | ||
"jest-mock": "^29.0.3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
要る?
要るとしてもdevDependenciesじゃないかしら
@@ -82,6 +88,7 @@ | |||
"node-fetch": "3.3.0", | |||
"nodemailer": "6.8.0", | |||
"nsfwjs": "2.4.2", | |||
"oauth": "^0.10.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
要る?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DiscordServerServiceとGithubServerServiceでは使われているけど
Fastifyと統合するのちょっと骨折れそう |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
YOSASOU
🙏🏻🙏🏻🙏🏻 |
🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 |
nodeLinker: pnpmだと型の不具合が起きるっぽい |
いやこれ peerDependencies に追加すれば解決する |
What
Migrate to Yarn Berry (v3.2.1)
Resolve #5858
Supersede #8472
Why
As yarn v3 (yarn berry) has worked with Misskey for a while and provides better performance when compiling while still retaining backwards compatibility with yarn v1, I feel that upgrading to yarn berry would be a smart choice.
Additional info
I've been building Misskey with yarn v3 for two months now both on my server for production and on my development machine with absolutely no problems. This PR was made simply by running
yarn
with yarn 3.2.1 and following the yarn migration instructions.Further steps