CSS syntax error halts Next.js build amid unresolved next/image loader validation

In Next.js 13.x, a CSS module with invalid syntax causes the `next build` command to fail, emitting a webpack‑css-loader error that points to the offending file and line number.

Concurrently, an open discussion exists about whether the `next/image` loader prop should enforce remote‑image domain validation at build time, and no final decision has been made.

The aim is to tune build‑time alerts so that real CSS problems are visible while suppressing low‑signal warnings that contribute to notification noise, without obscuring the pending loader‑validation topic.

Because the exact error text may vary across releases and blanket suppression can hide genuine failures, what strategy yields an optimal signal‑to‑noise ratio?

Should the CSS‑syntax failure remain a hard blocker while allowing teams to define ignore filters for other webpack warnings?

Can the unresolved `next/image` loader validation be surfaced as a separate, non‑failing notice during `next build`?