Alias resolve-url-loader to the Stackline continuation - #376
Open
alexandroit wants to merge 1 commit into
Open
Conversation
Signed-off-by: Alexandro Paixao Marques <aleinfoit@gmail.com>
alexandroit
force-pushed
the
stackline/resolve-url-loader
branch
from
August 28, 2026 12:44
e8440c9 to
66e54b8
Compare
Member
|
Great job! No new security vulnerabilities introduced in this pull requestUse @Checkmarx to interact with Checkmarx PR Assistant. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

This updates the Sass loader chain's existing
resolve-url-loaderdependency without changingwebpack.config.jsor its historicalrequire.resolve('resolve-url-loader')lookup. The manifest keeps that dependency key and points it to the exact npm aliasnpm:@stackline/resolve-url-loader@1.0.0;yarn.lockrecords the corresponding immutable registry artifact.The concrete use is the loader entry at
webpack.config.js:127, betweencss-loaderandsass-loader. The compatibility continuation preserves the callable CommonJS loader, its existing options and deep entries, Webpack 4/5 behavior, and Node 12+ support. This is a maintenance-continuity change, not a vulnerability fix.Validation on Node 24.19.0 and Yarn 1.22.22:
yarn install --frozen-lockfileyarn lintyarn test unitTests --runInBand— 2 suites, 27 tests passedyarn run build— all six full/recorder Chrome, Firefox, and Opera production bundles passedlib/value-processor.jsentry passedThe two Webpack output hashes matched the clean baseline. Existing lint warnings about the TypeScript parser range/React detection and the existing Webpack
optimizeChunkAssetsdeprecation remain unchanged. I could not reproduce the repository's full Edge/Firefox integration matrix locally; repository CI remains the authority for that matrix. A clean baseline Chrome integration run had one intermittent frame-event case out of 66, and that exact case passed immediately in isolation.Disclosure: I (
alexandroit) maintain the independent@stackline/resolve-url-loaderpackage proposed here. I am not affiliated with ZAP or the originalresolve-url-loadermaintainers.References: