Jira Issue

1. [Add links to jira issues]

Description

Issue

The project included package.json and package-lock.json files that were originally used as a reference for JavaScript packages manually installed in the static/js folder and for Dependabot vulnerability alerts. However:

• package.json was frequently out of sync with actual package versions in static/js
• Manual package management meant the dependency manifest wasn't reliable
• Recently added GitHub Actions tooling now directly scans JavaScript dependencies in the static/js folder, making package.json redundant

Solution

• Removed package.json and package-lock.json files
• Updated CONTRIBUTING.md development setup instructions:
  • Removed npm installation step
  • Updated Prettier usage to use npx prettier for manual formatting

Result

• Eliminates outdated/misleading dependency manifest
• JavaScript vulnerability scanning now handled directly by GitHub Actions
• Developers no longer need Node.js/npm installed locally
• JavaScript/CSS formatting still available via npx prettier

Checklist

• Tests added/updated
• Documentation updated (if needed)
• New strings prepared for translations

API Changes (if applicable)

• Permissions checked
• Endpoint tests added

Additional Notes

[Any other relevant information]