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

”ERROR [builder 8/9] RUN yarn build “when I run docker-compose build #9230

Closed
JiHeWeiHuan opened this issue Nov 25, 2022 · 3 comments · Fixed by #9239
Closed

”ERROR [builder 8/9] RUN yarn build “when I run docker-compose build #9230

JiHeWeiHuan opened this issue Nov 25, 2022 · 3 comments · Fixed by #9239
Labels
⚠️bug? This might be a bug

Comments

@JiHeWeiHuan
Copy link

💡 Actual Behavior

[builder 8/9] RUN yarn build:
#0 0.428 yarn run v1.22.19
#0 0.466 $ yarn workspaces foreach run build && yarn run gulp
#0 0.616 error Invalid subcommand. Try "info, run"
#0 0.616 info Visit https://yarnpkg.com/en/docs/cli/workspaces for documentation about this command.
#0 0.630 error Command failed with exit code 1.
#0 0.630 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

📝 Steps to Reproduce

docker-compose build

📌 Environment

Misskey version:12.119.0(Master Branch)
Your OS:Win11 22h2

@JiHeWeiHuan JiHeWeiHuan added the ⚠️bug? This might be a bug label Nov 25, 2022
@nykma
Copy link

nykma commented Nov 28, 2022

Same here. Yarn version v1.22.19.

@CyberRex0
Copy link
Contributor

Now Misskey uses yarn v3 and build commands are changed for its version but yarn version in container is still v1.
v3's commands are not supported in v1.

@bharath-naik
Copy link

facing same issue here. Thanks in advance

tamaina added a commit that referenced this issue Dec 5, 2022
* chore: Add yarn itself to repository

Fix #9230

* use yarn v3.3.0

Co-authored-by: tamaina <tamaina@hotmail.co.jp>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚠️bug? This might be a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants