Since they already had the low-level part (package manager), they only added a new module to handle workspaces whenever you have a pnpm-workspace. Its goal was to fill this gap of the easy-to-use and well-maintained monorepo tool we currently have.
You want to cache its cache between builds, not its outputs. pnpm introduced workspaces feature on v2. yarn/cache (or wherever your yarn config get cacheFolder is), and let Yarn rebuild node_modules/ on each build. Shop the JOANN fabric and craft store online to stock up for any project. IMO the "right" way to handle Yarn caching is to cache. I discovered a setup that might solve some of the above mentioned problems.
#Netlify yarn workspaces how to#
Time to take a break and try and see how to get it working locally with latest / greatest versions rather than relying on fixing things one-by-one from 2020.2:00:19 PM: build-image version: 653805ca4a64301556e56dc4b321ef8fc20cbb7cĢ:00:19 PM: buildbot version: ccda11705f87435917703d79785086e961e5d73cĢ:00:19 PM: Starting to download cache of 288.9MBĢ:00:20 PM: Finished downloading cache in 1.206042171sĢ:00:29 PM: Finished extracting cache in 9.180126006sĢ:00:29 PM: Finished fetching cache in 10.446618482sĢ:00:40 PM: Started restoring cached yarn cacheĢ:00:40 PM: Finished restoring cached yarn cacheĢ:00:44 PM: Started restoring workspace packages/scripts node modulesĢ:00:44 PM: Finished restoring workspace packages/scripts node modulesĢ:00:44 PM: Started restoring workspace packages/studio node modulesĢ:00:44 PM: Finished restoring workspace packages/studio node modulesĢ:00:44 PM: Started restoring workspace root node modulesĢ:00:44 PM: Finished restoring workspace root node modulesĢ:00:45 PM: Installing NPM modules using Yarn version 2.4.2Ģ:00:46 PM: ➤ YN0050: The cache-folder option has been deprecated use rc settings insteadĢ:01:32 PM: ➤ YN0013: │ 4 packages were already cached, 1532 had to be fetchedĢ:01:32 PM: ➤ YN0000: └ Completed in 45s 880msĢ:02:50 PM: Started saving workspace packages/scripts node modulesĢ:02:50 PM: Finished saving workspace packages/scripts node modulesĢ:02:50 PM: Started saving workspace packages/studio node modulesĢ:02:50 PM: Finished saving workspace packages/studio node modulesĢ:02:50 PM: Started saving workspace root node modulesĢ:02:50 PM: Finished saving workspace root node modules I experimented with Yarn Workspaces and Netlify's recently released better support for monorepos (netlify.toml per site in subdirectory). I am going to set it to yarn 1.22 and rebuild.ġ0:22:00 AM: gyp ERR! stack Error: `make` failed with exit code: 2ġ0:22:00 AM: gyp ERR! stack at ChildProcess.onExit (/opt/buildhome/.nvm/versions/node/v12.22.9/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)ġ0:22:00 AM: gyp ERR! stack at ChildProcess.emit (events.js:314:20)ġ0:22:00 AM: gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)ġ0:22:00 AM: gyp ERR! System Linux 5.4.129+ġ0:22:00 AM: gyp ERR! command "/opt/buildhome/.nvm/versions/node/v12.22.9/bin/node" "/opt/buildhome/.nvm/versions/node/v12.22.9/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"ġ0:22:00 AM: gyp ERR! cwd /opt/build/repo/node_modules/sharpġ0:22:00 AM: info Visit for documentation about this command.
#Netlify yarn workspaces install#
I am not sure why it is trying to install that when the default should be yarn 1.22 per the docs.
Specifically I am running into issues with yarn 1.17.
The blog post does a good job of describing the issues that I am running into with the new build image. same with other npm run commands from package.json.npm run dev - works locally on macOS 12.1 – serving content at.
9:40:44 AM: mv: cannot stat '/opt/buildhome/.yarn': No such file or directoryĩ:40:44 AM: Started restoring cached node modulesĩ:40:44 AM: Finished restoring cached node modulesĩ:40:44 AM: /opt/build-bin/run-build-functions.sh: line 141: yarn: command not foundĩ:40:44 AM: Installing NPM modules using Yarn versionĩ:40:44 AM: /opt/build-bin/run-build-functions.sh: line 152: yarn: command not foundĩ:40:44 AM: Build was terminated: Build script returned non-zero exit code: 1
0 kommentar(er)
