Update package.json

[perploug]

aaaaaaaaaaaaaaaaaSigned-off-by: Per Ploug [email protected]

One-line summaryjjjjjaaaaasdaaaa

aaa

Issue : #1 (only if appropriate) - lets reopen again

Description

A few sentences describing the overall goals of the pull request's commits.

Types of Changes

What types of changes does your code introduce? Keep the ones that apply:

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Configuration change
• Refactor/improvements
• Documentation / non-code

Tasks

List of tasks you will do to complete the PR

• [ ] Created Task 1
• [ ] Created Task 2
• [ ] To-do Task 3

Review

List of tasks the reviewer must do to review the PR

• [ ] Tests
• [ ] Documentation
• [ ] CHANGELOG

Deployment Notes

These should highlight any db migrations, feature toggles, etc. jjjaaaaaasaaaaaaaaaaaaaaaaaa

[zincr[bot]]

🤖 zincr found 1 problem , 1 warning

❌ Approvals
ℹ️ Dependency Licensing

Details on how to resolve are provided below

---

Approvals

All proposed changes must be reviewed by project maintainers before they can be merged

Not enough people have approved this pull request - please ensure that 1 additional user, who have not contributed to this pull request approve the changes.

• ✅ Approved by PR author @perploug
• ❌ 1 additional approval needed  

Dependency Licensing

All dependencies specified in package manager files must be reviewed, banned dependency licenses will block the merge, all new dependencies introduced in this pull request will give a warning, but not block the merge

Please ensure that only dependencies with licenses compatible with the license of this project is included in the pull request.

• ℹ️ Could not process package.json for new dependencies