You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prefacing this with the warning that this might be an upstream volto issue, as it is a problem that is coming from the startup of the volto instance in core.
I've tried the reproduction steps with node20 (unsupported by Volto 19 but is the pinned version for volto-hydra), node22 and node 24. I have tried pnpm 9, 10 (pinned by hydra) and 11 (latest). This may be some weird local issue, but it's occuring on any instance I try to start.
Steps to reproduce
git clone git@github.com:collective/volto-hydra
cd volto-hydra && make install
make start
### Optional step after failed make start
pnpm build:deps
Additional info
Running make start produces the following error:
ERROR Invalid razzle.config.js file.
Error: Cannot find module 'REDACTED/volto-hydra/core/packages/volto/node_modules/@plone/registry/dist/addon-registry/create-addons-loader.cjs'
at createEsmNotFoundErr (node:internal/modules/cjs/loader:1249:15)
at finalizeEsmResolution (node:internal/modules/cjs/loader:1237:15)
at resolveExports (node:internal/modules/cjs/loader:636:14)
at Module._findPath (node:internal/modules/cjs/loader:716:31)
at Module._resolveFilename (node:internal/modules/cjs/loader:1198:27)
at Module._load (node:internal/modules/cjs/loader:1043:27)
at Module.require (node:internal/modules/cjs/loader:1298:19)
at require (node:internal/modules/helpers:182:18)
at Object.<anonymous> (REDACTED/volto-hydra/core/packages/volto/razzle.config.js:11:32)
at Module._compile (node:internal/modules/cjs/loader:1529:14) {
code: 'MODULE_NOT_FOUND',
path: 'REDACTED/volto-hydra/core/packages/volto/node_modules/@plone/registry/package.json'
}
ELIFECYCLE Command failed with exit code 1.
make: *** [Makefile:41: start] Error 1
This is due to the volto core not having the modules built. So after running the optional next steps to see if we can get around this issue, the following error is produced:
This occurs because the lightningcss that is installed is the stub "This file is required so that npm creates the lightningcss binary on Windows." file and doesn't seem to get substituted for the real binary. Manually running the postinstall.js script with node at /node_modules/.pnpm/lightningcss-cli@1.32.0/node_modules/lightningcss-cli/postinstall.js runs this substitution and then it builds correctly, solving the issue. The expectation is that all this happens at install time, however it doesn't seem to be running for some reason, causing a silent failure on the startup. The allowBuilds key within pnpm-workspace.yaml doesn't seem to have any effect on this running.
## Proposed solution
For now, add a manual step to make install which runs this to workaround the issue
Prefacing this with the warning that this might be an upstream volto issue, as it is a problem that is coming from the startup of the volto instance in core.
I've tried the reproduction steps with node20 (unsupported by Volto 19 but is the pinned version for volto-hydra), node22 and node 24. I have tried pnpm 9, 10 (pinned by hydra) and 11 (latest). This may be some weird local issue, but it's occuring on any instance I try to start.
Steps to reproduce
git clone git@github.com:collective/volto-hydracd volto-hydra && make installmake start### Optional step after failed
make startpnpm build:depsAdditional info
Running
make startproduces the following error:This is due to the volto core not having the modules built. So after running the optional next steps to see if we can get around this issue, the following error is produced:
This occurs because the lightningcss that is installed is the stub
"This file is required so that npm creates the lightningcss binary on Windows."file and doesn't seem to get substituted for the real binary. Manually running thepostinstall.jsscript with node at/node_modules/.pnpm/lightningcss-cli@1.32.0/node_modules/lightningcss-cli/postinstall.jsruns this substitution and then it builds correctly, solving the issue. The expectation is that all this happens at install time, however it doesn't seem to be running for some reason, causing a silent failure on the startup. TheallowBuildskey withinpnpm-workspace.yamldoesn't seem to have any effect on this running.## Proposed solution
make installwhich runs this to workaround the issueSystem info
node -e "console.log('platform:', process.platform, '| arch:', process.arch)")uname -moutputsx86_64to rule out arch.