Skip to content

DRAFT: Update build packages.#81

Open
green-br wants to merge 3 commits intoOpenCHAMI:mainfrom
green-br:update_packages
Open

DRAFT: Update build packages.#81
green-br wants to merge 3 commits intoOpenCHAMI:mainfrom
green-br:update_packages

Conversation

@green-br
Copy link
Contributor

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
Copy link
Member

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

@green-br
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants