Hi there,
I’m using sage 10 theme for one of my website. On running yarn command it’s taking too long to build: @roots/bud-framework@npm:6.23.3, @swc/core@npm:1.7.2 & core-js-pure@npm:3.41.0
Below is the message that it keep on showing for a long:
➤ YN0000: · Yarn 4.7.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 310ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 1s 138ms
➤ YN0000: ┌ Link step
➤ YN0007: │ @roots/bud-framework@npm:6.23.3 must be built because it never has been before or the last one failed
➤ YN0007: │ @swc/core@npm:1.7.2 [e7bb3] must be built because it never has been before or the last one failed
➤ YN0007: │ core-js-pure@npm:3.41.0 must be built because it never has been before or the last one failed
I’m running it on
node v21.7.3 (with npm v10.5.0)
yarn v4.7.0
Yarn build and other commands are either too long.
My package.json looks like:
{
"name": "sage",
"private": true,
"browserslist": [
"extends @roots/browserslist-config"
],
"engines": {
"node": ">=20.0.0"
},
"type": "module",
"scripts": {
"dev": "bud dev",
"build": "bud build",
"translate": "npm run translate:pot && npm run translate:update",
"translate:pot": "wp i18n make-pot . ./resources/lang/sage.pot --include=\"theme.json,patterns,app,resources\"",
"translate:update": "for file in ./resources/lang/*.po; do wp i18n update-po ./resources/lang/sage.pot $file; done",
"translate:compile": "npm run translate:mo && npm run translate:js",
"translate:js": "wp i18n make-json ./resources/lang --pretty-print",
"translate:mo": "wp i18n make-mo ./resources/lang ./resources/lang"
},
"devDependencies": {
"@roots/bud": "6.23.3",
"@roots/bud-tailwindcss": "6.23.3",
"@roots/sage": "6.23.3"
},
"dependencies": {
"gsap": "^3.12.5",
"imagesloaded": "^5.0.0",
"react": "^19.0.0",
"react-dom": "^19.0.0",
"react-phone-number-input": "^3.4.8",
"split-type": "^0.3.4",
"swiper": "^11.1.14"
}
}
Can anyone suggest a workaround or a fix for this ?