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
Describe the bug
The Mirage 2 theme in DSpace 6.x relies on grunt to run tasks during the frontend build. A few weeks ago grunt was updated 1.6.0, which requires Node.js v16. This breaks the build because Mirage 2 is limited to Node.js v14:
error grunt@1.6.1: The engine "node" is incompatible with this module. Expected version ">=16". Got "14.21.2"
DSpace 6 is nearing end of life, but the solution is to pin grunt to version 1.5.x using the ~1.5.3 semver specifier in dspace-xmlui-mirage2/src/main/webapp/package.json.
The text was updated successfully, but these errors were encountered:
@alanorth : If you wanted to provide a quick fix, we could patch this in dspace-6_x for now & perhaps cut one last (small, important fixes only) 6.x release prior to EOL.
That said, if it's not a priority for you, that's perfectly OK as well. This ticket provides enough clues for anyone to patch this themselves if they are impacted.
Grunt 1.6.0 updated its Node.js dependency to version 16. Mirage 2
is a legacy theme that is stuck on Node.js 14, so this breaks the
build. Pin the grunt version to the last 1.5.x release providing
support for Node.js 14 using semver's ~1.5.3 specifier.
Fixes: DSpace#8676
Describe the bug
The Mirage 2 theme in DSpace 6.x relies on grunt to run tasks during the frontend build. A few weeks ago grunt was updated 1.6.0, which requires Node.js v16. This breaks the build because Mirage 2 is limited to Node.js v14:
error grunt@1.6.1: The engine "node" is incompatible with this module. Expected version ">=16". Got "14.21.2"
DSpace 6 is nearing end of life, but the solution is to pin grunt to version 1.5.x using the
~1.5.3
semver specifier indspace-xmlui-mirage2/src/main/webapp/package.json
.The text was updated successfully, but these errors were encountered: