Provide offending asset path in JS/CSS preprocess error.

Created on 8 September 2025, 14 days ago

Problem/Motivation

Currently, when the JS/CSS optimization throws an error, no information is provided about the actual asset that offends it.

Steps to reproduce

Create a library with assets that are getting preprocessed, but no "preprocess" is set in the library settings. When an attempt to load the aggregated js or css file happens, the error will result.

Proposed resolution

Add a path from the library definition to the error description, to inform the user about what precisely asset is causing the error.

Remaining tasks

Review

Feature request
Status

Active

Version

11.2 🔥

Component

asset library system

Created by

🇧🇬Bulgaria alexrayu

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024