← All tasks
javascriptwebpack/css-loader #1567Not a task: already works

Remove `webpack` from `peerDependencies`

envgap__webpack__css-loader-1567

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.
Not a benchmark task.
  • The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit
6f439299838eab7e6fb18f6e9f47b9dee2208463
Manifest
package.json
Reproduce
Awaiting issue-specific recipe
Run under trace
Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

webpack/css-loader #1567 · read the original issue
### Modification Proposal



We are using `css-loader` with `rsbuild`. This means, we don't use webpack directly anymore / don't have it installed. `css-loader` still works fine with the setup, but when doing a `yarn install`, yarn complains about not having `webpack` listed in our dependencies.



> ➤ YN0002: │ my-awesome-rsbuild-webapp doesn't provide webpack (p1ea2d), requested by css-loader.



As `css-loader` doesn't use `webpack` directly, I think it's ok to just remove it from the `peerDependencies` array.



### Expected Behavior / Situation



The loader will behave the same, but in the context of `rsbuild` won't add a warning in the install logs.



### Actual Behavior / Situation



A warning in the install logs:



> ➤ YN0002: │ my-awesome-rsbuild-webapp doesn't provide webpack (p1ea2d), requested by css-loader.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched
[]