OHIF 3.8 Build Issues on M1 Mac with Node 18 and Yarn 3

[alireza]

View in #ohif on Slack

@Chris_Hafey: still unable to get ohif 3.8 to build. I am using node 18.16.0 and yarn 1.22.22 on M1 Mac and get 100+ lines of messages:
➤ YN0000: ┌ Fetch step
➤ YN0013: │ yocto-queue@npm:0.1.0 can’t be found in the cache and will be fetch
➤ YN0013: │ yocto-queue@npm:1.0.0 can’t be found in the cache and will be fetch
➤ YN0013: │ zstddec@npm:0.1.0 can’t be found in the cache and will be fetched f
➤ YN0013: │ zwitch@npm:1.0.5 can’t be found in the cache and will be fetched fr
➤ YN0013: │ zwitch@npm:2.0.4 can’t be found in the cache and will be fetched fr
➤ YN0000: └ Completed in 1s 921ms
➤ YN0000: ┌ Link step
➤ YN0007: │ core-js@npm:3.36.1 must be built because it never has been before or the last one failed
➤ YN0007: │ husky@npm:3.1.0 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:2.6.12 must be built because it never has been before or the last one failed
➤ YN0007: │ swiper@npm:8.4.7 must be built because it never has been before or the last one failed
➤ YN0007: │ cypress@npm:13.7.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @parcel/watcher@npm:2.0.4 must be built because it never has been before or the last one failed
➤ YN0007: │ esbuild@npm:0.18.20 must be built because it never has been before or the last one failed
➤ YN0007: │ @swc/core@npm:1.4.13 [93de3] must be built because it never has been before or the last one failed
➤ YN0007: │ core-js-pure@npm:3.36.1 must be built because it never has been before or the last one failed
➤ YN0007: │ sharp@npm:0.32.6 must be built because it never has been before or the last one failed
➤ YN0007: │ nx@npm:16.10.0 [cc223] must be built because it never has been before or the last one failed
➤ YN0007: │ ohif-monorepo-root@workspace:. must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 31s 913ms
➤ YN0000: Done with warnings in 48s 507ms

@Alireza_Sedghi: Seems like the log from yarn 3 , would you please use yarn 1.x

[alireza]

View in #ohif on Slack

@Chris_Hafey: This is the latest release right? I would expect it to “just work”. Would be much more professional to reduce the number of messages this generates on build

@Alireza_Sedghi: I’m not sure why your system thinks it should use yarn 3
we have fixed it here

"engines": {
    "node": ">=18",
    "npm": ">=6",
    "yarn": ">=1.20.0"
  },

@Chris_Hafey: maybe make the yarn a range for 1.2? It is accepting 3.x

@Alireza_Sedghi: Ok i will do that
does it work using 1.x?

@Chris_Hafey: trying to install 1.x, but yarnpkg website has been kind of broken the past week so not sure the commands. Might be good to add those commands to the docs?
npm i yarn installs 3.x

@Alireza_Sedghi: I think they changed that recently
yarn versions is a mess
1.x was stable and is
no one knows what is 2.x
3 was on the right track
but they are now on 4.x

@Chris_Hafey: OK think I have the right version installed now:
npm i -g yarn
yarn set version classic
trying…
ahh so just figured this out - yarn set version classic sets some kind of variable in a file and is cleared when you do git clean -dfx reverting back to 3.x. that must be why i had so much trouble. I assumed it would be stored globally
looks to be building better now
Looks like its working!