Update dependency file-loader to v5.1.0 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
file-loader	5.0.2 -> 5.1.0

---

Release Notes

webpack-contrib/file-loader (file-loader)

v5.1.0

Compare Source

Features

• support the query template for the name option (#​366) (cd8698b)

5.0.2 (2019-11-25)

Chore

• add the funding field in package.json

5.0.1 (2019-11-25)

Bug Fixes

• name of esModule option in source code (#​346) (31d6589)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pils-frontend/package-lock.json

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: undefined@undefined
npm ERR! Found: webpack@3.12.0
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"3.12.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.0.0 || ^5.0.0" from file-loader@5.1.0
npm ERR! node_modules/file-loader
npm ERR!   dev file-loader@"5.1.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/1b4392/3a0723/cache/others/npm/_logs/2023-08-07T19_49_44_185Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/1b4392/3a0723/cache/others/npm/_logs/2023-08-07T19_49_44_185Z-debug-0.log

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (85cc939) 22.34% compared to head (95d8f5f) 22.34%.
Report is 2 commits behind head on main.

❗ Current head 95d8f5f differs from pull request most recent head fc78fc1. Consider uploading reports for the commit fc78fc1 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1050   +/-   ##
=======================================
  Coverage   22.34%   22.34%           
=======================================
  Files          14       14           
  Lines         179      179           
  Branches       21       21           
=======================================
  Hits           40       40           
  Misses        121      121           
  Partials       18       18           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication