[stable5.5] Fix npm audit

[nextcloud-command]

Audit report

This audit fix resolves 2 of the total 24 vulnerabilities found in your project.

Updated dependencies

• @nextcloud/webpack-vue-config
• @playwright/test

Fixed vulnerabilities

@nextcloud/webpack-vue-config #

• Caused by vulnerable dependency:
  • vue
  • vue-loader
  • vue-template-compiler
• Affected versions: <=6.2.0
• Package usage:
  • node_modules/@nextcloud/webpack-vue-config

@playwright/test #

• Caused by vulnerable dependency:
  • playwright
• Affected versions: 0.9.7 - 0.1112.0-alpha2 || 1.38.0-alpha-1692262648000 - 1.55.1-beta-1758616458000
• Package usage:
  • node_modules/@playwright/test

[codecov[bot]]

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 14.61%. Comparing base (b67b40e) to head (13c248f). :warning: Report is 3 commits behind head on stable5.5.

Additional details and impacted files

@@            Coverage Diff             @@
##           stable5.5    #7563   +/-   ##
==========================================
  Coverage      14.61%   14.61%           
==========================================
  Files            209      209           
  Lines          10149    10149           
  Branches        2459     2460    +1     
==========================================
  Hits            1483     1483           
  Misses          8317     8317           
  Partials         349      349           

Flag	Coverage Δ
javascript	14.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[SebastianKrupinski]

Hi @st3iny

Thanks for the assist! I was thinking of migrating it to vitest actually as this is becoming a constant problem.