DRAFT: Update build packages.

[green-br]

Pull Request Template

Thank you for your contribution! Please ensure the following before submitting:

Checklist

• My code follows the style guidelines of this project
• I have added/updated comments where needed
• I have added tests that prove my fix is effective or my feature works
• I have run make test (or equivalent) locally and all tests pass
• DCO Sign-off: All commits are signed off (git commit -s) with my real name and email
• REUSE Compliance:
  • Each new/modified source file has SPDX copyright and license headers
  • Any non-commentable files include a <filename>.license sidecar
  • All referenced licenses are present in the LICENSES/ directory

Description

Please include a summary of the change and which issue is fixed.
Also include relevant motivation and context.

When building the site the packages are listed as out of date. This attempts to update the npm packages.

Still in draft due to needing to check pnpm configuration and deployment.

Fixes a couple of files with syntax errors which error on latest versions.

Currently using a patch to doks-core to properly handle pages without contributors and with email address with more than 2 domains.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

---

For more info, see Contributing Guidelines.

[alexlovelltroy]

Lots of changes in here that go beyond bumping some versions. Were those necessary with the new versions or something?

[green-br]

Lots of changes in here that go beyond bumping some versions. Were those necessary with the new versions or something?

Many of the packages in use have become dormant (along with vulnerabilities) so had to try and replace with more active equivalents. I decided to create an empty project and then migrate the files across to make sure we had a consistent up-to-date configuration. I am not a npm expert so may be other ways to achieve this - I will try minimising the changes to see if we can just migrate across some of the config without large changes.

[green-br]

Used new approach to try and reduce changing content of files too much (but had to move files unfortunately).

1. Hyas theme is now not being maintained and moved to thulite
2. Theme has different locations for partials so renamed directories.
3. Removed old hugo dependency which was causing old vulnerable packages to be used. Hugo-installer is all you need.
4. Changed ordering in mounts to get the correct precedence so local layout takes precedence.
5. Updating postcss.config.js which seems to come bundled when setting up new theme.
6. Fixed a couple of typos causing the processing to fail.
7. Updated version of hugo used by hugo-installer. Unfortunately more recent hugo versions, the hugo-installer failed on Mac due to change in filename in https://github.com/gohugoio/hugo project (moved from tar.gz to pkg).
8. Used pnpm to update local file but seems to only be used in netlify and not clear if that still being used?

Rendered locally and could see no change in behaviour.

[green-br]

Have updated Node to use to 20 in validate PR action. Seems deploy action uses Node 20 (seems based on OS provided version) whilst validate PR uses node 18. I think it's save to upgrade validate action to to node 20. Possibly should specify version of Node in deploy action.

[alexlovelltroy]

I added a commit to my own branch that upgrades hugo and replaced the hugo installer with one that is still maintained

https://github.com/OpenCHAMI/openchami.org/tree/update_packages

[green-br]

I added a commit to my own branch that upgrades hugo and replaced the hugo installer with one that is still maintained

https://github.com/OpenCHAMI/openchami.org/tree/update_packages

Thanks - if I haven't managed to mess it up I have merged your change into my branch.